lkml.org 
[lkml]   [2009]   [Jul]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC][PATCH] Check write to slab memory which freed already using mudflap
On Fri, 10 Jul 2009, Pekka Enberg wrote:

> Hey, I said SLAB is on its way out (yes, it really is). But I didn't say
> we're going to blindly remove it if performs better than the
> alternatives. I don't see any reason why SQLB can't reach the same
> performance as SLAB after on fundamental level, though. Can you?
>

I'm not really interested in making predictions on which design has the
greatest potential for pure performance, I'm interested in what is proven
to work and does the job better than any alternative. Right now, for
certain workloads, that's undeniably slab. So I'd disagree that slab is
on its way out until another allocator is shown to at least have parity
with it (at which time I'd become more interested in the cleanliness of
the code, the debugging support, etc.).

It's my opinion that slab is on its way out when there's no benchmark that
shows it is superior by any significant amount. If that happens (and if
its successor is slub, slqb, or a yet to be implemented allocator), we can
probably start a discussion on what's in and what's out at that time.


\
 
 \ /
  Last update: 2009-07-10 12:05    [from the cache]
©2003-2011 Jasper Spaans