[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090708184418.GB16090@redhat.com>
Date: Wed, 8 Jul 2009 14:44:18 -0400
From: Dave Jones <davej@...hat.com>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc: Joao Correia <joaomiguelcorreia@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Américo Wang <xiyou.wangcong@...il.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Arjan van de Ven <arjan@...ux.intel.com>,
Catalin Marinas <catalin.marinas@....com>
Subject: Re: [PATCH 1/3] Increase lockdep limits: MAX_STACK_TRACE_ENTRIES
On Wed, Jul 08, 2009 at 08:36:04PM +0200, Peter Zijlstra wrote:
> Looking at a lockdep dump hch gave me I can see that that is certainly
> possible, I see tons of very deep callchains.
>
> /me wonders if we're getting significantly deeper..
>
> OK I guess we can raise this one, does doubling work? That would get us
> around 29 entries per trace..
>
> Also, Dave do these distro init scrips still load every module on the
> planet or are we more sensible these days?
> module load/unload cycles are really bad for lockdep resources.
34 modules get loaded on the system I saw the trace on.
(That's from lsmod after fulling booting up). I'm not aware of any
module unloading that happens during bootup.
Dave
--
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