[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080104024506.GA4665@one.firstfloor.org>
Date: Fri, 4 Jan 2008 03:45:06 +0100
From: Andi Kleen <andi@...stfloor.org>
To: Christoph Lameter <clameter@....com>
Cc: Matt Mackall <mpm@...enic.com>, Ingo Molnar <mingo@...e.hu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Pekka Enberg <penberg@...helsinki.fi>,
Hugh Dickins <hugh@...itas.com>,
Andi Kleen <andi@...stfloor.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] procfs: provide slub's /proc/slabinfo
> I still have trouble to see that SLOB still has much to offer. An embedded
> allocator that in many cases has more allocation overhead than the default
> one? Ok you still have advantages if allocations are rounded up to the
> next power of two for a kmalloc and because of the combining of different
> types of allocations in a single slab if there are an overall small number
> of allocations. If one would create a custom slab for the worst problems
> there then this may also go away.
I suspect it would be a good idea anyways to reevaluate the power of two
slabs. Perhaps a better distribution can be found based on some profiling?
I did profile kmalloc using a systemtap script some time ago but don't
remember the results exactly, but iirc it looked like it could be improved.
A long time ago i also had some code to let the network stack give hints
about its MMUs to slab to create fitting slabs for packets. But that
was never really pushed forward because it turned out it didn't help
much for the most common 1.5K MTU -- always only two packets fit into
a page.
-Andi
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists