Re: SLUB sysfs support

Christoph Lameter
2007-12-28T02:19:58Z

On Fri, 28 Dec 2007, Al Viro wrote:

> Oh, lovely. So we can have module A do kmem_cache_create(), calling
> cache "foo". Then module B does (without any knowlegde about A)
> completely unrelated kmem_cache_create(), calling the sucker "bar".
> mm/slub decides that they are mergable. Then we get rmmod A... and
> no way to find out if that's foo or bar going away - kmem_cache_destroy()
> doesn't have enough information to figure that out. So we have to keep
> both slab/foo and slab/bar around until both are gone or until somebody
> kind enough creates a cache called foo. Better yet, on some systems you
> get things like slab/nfsd4_delegations sticking around long after nfsd is
> gone just because slub.c decides that it's sharable, but in the next
> kernel version the thing it's shared with gets different object size and
> behaviour suddenly changes - now it's gone as soon as nfsd is gone.
> Brilliant interface, that...

Just enable slab debugging and all of that goes away and you get the usual
error messages. Otherwise slub tries to compress the memory use as much as
possible. The advantage here is that you can add an abitrary amount of
kmem_cache_create() without increasing memory use significantly. Its cheap
to do kmem_cache creations. Thus you can create open arbitrary caches not
worrying about memory use and have meaningful variables on which you do
kmem_cache_alloc instead of kmalloc/kfree. kmalloc/kfree wastes space
since they go to powers of two. And kmalloc/kfree have to calculate the
cache at runtime whereas kmem_cache_alloc/free does the lookup once.

The amount of per cpu stuff we keep around that is idle is reduced by 50%.
Increasing cpu cache usage and reduces memory footprint. per cpu stuff
has to hold per cpu reserves and it is not good to waste too much memory
there.

nfsd4_delegations? What is this about?

How do I scan for the symlinks in sysfs?