Quoting Serge E. Hallyn ([email protected]):
> Quoting Andi Kleen ([email protected]):
> > On Tuesday 02 May 2006 19:20, Serge E. Hallyn wrote:
> > > > With many name spaces you would have smaller task_struct, less cache
> > > > foot print, better cache use of task_struct because slab cache colouring
> > > > will still work etc.
> > >
> > > I suppose we could run some performance tests with some dummy namespace
> > > pointers? 9 void *'s directly in the task struct, and the same inside a
> > > refcounted container struct. The results might add some urgency to
> > > implementing the struct nsproxy.
> >
> > Not sure you'll notice too much difference on the beginning. I am just
>
> 9 void*'s is probably more than we'll need, though, so it's not "the
> beginning". Eric previously mentioned uts, sysvipc, net, pid, and uid,
> to which we might add proc, sysctl, and signals, though those are
> probably just implied through the others.
>
> What others do you see us needing?
>
> If the number were more likely to be 50, then in the above experiment
> use 50 instead - the point was to see the performance implications
> without implementing the namespaces first.
>
> Anyway I guess I'll go ahead and queue up some tests.
Though of course one reason those tests won't be very meaningful is that
the void*'s won't be being dereferenced, so we won't be accounting for
the performance hit of the double dereference and resulting cache
hits...
-serge
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
