[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1259082756.17871.607.camel@calx>
Date: Tue, 24 Nov 2009 11:12:36 -0600
From: Matt Mackall <mpm@...enic.com>
To: paulmck@...ux.vnet.ibm.com
Cc: Peter Zijlstra <peterz@...radead.org>,
Pekka Enberg <penberg@...helsinki.fi>, linux-mm@...ck.org,
cl@...ux-foundation.org, LKML <linux-kernel@...r.kernel.org>,
Nick Piggin <npiggin@...e.de>
Subject: Re: lockdep complaints in slab allocator
On Tue, 2009-11-24 at 09:00 -0800, Paul E. McKenney wrote:
> On Tue, Nov 24, 2009 at 05:33:26PM +0100, Peter Zijlstra wrote:
> > On Mon, 2009-11-23 at 21:13 +0200, Pekka Enberg wrote:
> > > Matt Mackall wrote:
> > > > This seems like a lot of work to paper over a lockdep false positive in
> > > > code that should be firmly in the maintenance end of its lifecycle? I'd
> > > > rather the fix or papering over happen in lockdep.
> > >
> > > True that. Is __raw_spin_lock() out of question, Peter?-) Passing the
> > > state is pretty invasive because of the kmem_cache_free() call in
> > > slab_destroy(). We re-enter the slab allocator from the outer edges
> > > which makes spin_lock_nested() very inconvenient.
> >
> > I'm perfectly fine with letting the thing be as it is, its apparently
> > not something that triggers very often, and since slab will be killed
> > off soon, who cares.
>
> Which of the alternatives to slab should I be testing with, then?
I'm guessing your system is in the minority that has more than $10 worth
of RAM, which means you should probably be evaluating SLUB.
--
http://selenic.com : development and support for Mercurial and Linux
--
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