Re: [RFC PATCH] greatly reduce SLOB external fragmentation

Matt Mackall
2008-01-10T19:25:19Z

On Thu, 2008-01-10 at 11:16 -0800, Christoph Lameter wrote:
> On Thu, 10 Jan 2008, Matt Mackall wrote:
>
> > Here I'm going to differ with you. The premises of the SLAB concept
> > (from the original paper) are:
> >
> > a) fragmentation of conventional allocators gets worse over time
>
> Even fragmentation of SLAB/SLUB gets worses over time. That is why we need
> a defrag solution.
>
> > b) grouping objects of the same -type- (not size) together should mean
> > they have similar lifetimes and thereby keep fragmentation low
>
> I agree that is crap. The lifetimes argument is mostly only exploitable in
> benchmarks. That is why SLUB just groups them by size if possible.
>
> > d) constructors and destructors are cache-friendly
>
> I agree. Crap too. We removed the destructors. The constructors are needed
> so that objects in slab pages always have a definite state. That is f.e.
> necessary for slab defragmentation because it has to be able to inspect an
> object at an arbitrary time and either remove it or move it to another
> slab page.

Are you saying that the state of -freed- objects matters for your active
defragmentation? That's odd.

> Constructors also make sense because the initialization of a cache object
> may be expensive. Initializing list heads and spinlocks can take some code
> and that code can be omitted if objects have a definite state when they
> are free. We saw that when measuring the buffer_head constructors effect
> on performance.

Hmm. SLOB proves that you don't need to segregate objects based on
constructors, so you could combine even slabs that have constructors and
just delay construction until allocation. I'm surprised constructors
have measurable advantage..

--
Mathematics is the supreme nostalgia of our time.