[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84144f020911241316q704d0677m9fe9e2689948903b@mail.gmail.com>
Date: Tue, 24 Nov 2009 23:16:08 +0200
From: Pekka Enberg <penberg@...helsinki.fi>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Matt Mackall <mpm@...enic.com>, paulmck@...ux.vnet.ibm.com,
linux-mm@...ck.org, cl@...ux-foundation.org,
LKML <linux-kernel@...r.kernel.org>,
Nick Piggin <npiggin@...e.de>,
David Rientjes <rientjes@...gle.com>
Subject: Re: lockdep complaints in slab allocator
On Tue, Nov 24, 2009 at 11:01 PM, Peter Zijlstra <peterz@...radead.org> wrote:
>> If there's a proposal here, it's not clear what it is.
>
> Merge SLQB and rm mm/sl[ua]b.c include/linux/sl[ua]b.h for .33-rc1
>
> As long as people have a choice they'll not even try new stuff and if
> they do they'll change to the old one as soon as they find an issue, not
> even bothering to report, let alone expend effort fixing it.
Oh, no, SLQB is by no means stable enough for the general public. And
it doesn't even have all the functionality SLAB and SLUB does (cpusets
come to mind).
If people want to really help us getting out of this mess, please take
a stab at fixing any of the outstanding performance regressions for
either SLQB or SLUB. David's a great source if you're interested in
knowing where to look. The only big regression for SLUB is the Intel
TPC benchmark thingy that nobody (except Intel folks) really has
access to. SLQB doesn't suffer from that because Nick had some
performance testing help from Intel IIRC.
--
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