Re: Patch workqueue: create new slab cache instead of hacking

From: Christoph Lameter
Date: Wed Mar 21 2012 - 14:20:17 EST


On Wed, 21 Mar 2012, Eric Dumazet wrote:

> On Wed, 2012-03-21 at 12:54 -0500, Christoph Lameter wrote:
> > On Wed, 21 Mar 2012, Eric Dumazet wrote:
> >
> > > On Wed, 2012-03-21 at 10:03 -0500, Christoph Lameter wrote:
> > > > On Wed, 21 Mar 2012, Eric Dumazet wrote:
> > > >
> > > > > Creating a dedicated cache for few objects ? Thats a lot of overhead, at
> > > > > least for SLAB (no merges of caches)
> > > >
> > > > Its some overhead for SLAB (a lot is what? If you tune down the per cpu
> > > > caches it should be a couple of pages) but its none for SLUB.
> > >
> > > SLAB overhead per cache is O(CPUS * nr_node_ids) (unless alien caches
> > > are disabled)
> >
> > nr_node_ids==2 in the standard case these days. Alien caches are minimal.
>
>
> Thats not true. Some machines use lots of nodes (fake nodes) for various
> reasons.

Which is not a typical use case.

> And they cant disable alien caches for performance reasons.

Ok then lets genericize the slub merge in some form so that it works for
all slab allocators.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/