Messages in this thread | | | Subject | Re: [RFC][PATCH] Check write to slab memory which freed already using mudflap | From | Pekka Enberg <> | Date | Fri, 10 Jul 2009 12:40:26 +0300 |
| |
Hi Nick,
On Fri, 2009-07-10 at 11:29 +0200, Nick Piggin wrote: > What I would like to see is we eventualy make the hard decision > and cull 2 of them. If SLQB is not clearly better (or, if it is > clearly worse) than the other allocators and it can't be improved, > then it has failed my goals for it and I would prefer to remove it > from the tree.
I'm not sure it's such a hard decision. SLAB is on it's way out because SLUB and SLQB code are much cleaner and the debugging support is better. As for SLUB vs. SLQB, I'm hoping to trick you, Mel, and others into doing an "epic slab allocator performance battle" and post the numbers once we have have everything merged to mainline. My gut feeling is that SLQB is in the lead because SLUB hasn't addressed the Intel regression.
Pekka
| |