From: Dave Jones <davej@redhat.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: "Joao Correia" <joaomiguelcorreia@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Américo Wang" <xiyou.wangcong@gmail.com>,
"Frederic Weisbecker" <fweisbec@gmail.com>,
"Arjan van de Ven" <arjan@linux.intel.com>,
"Catalin Marinas" <catalin.marinas@arm.com>
Subject: Re: [PATCH 1/3] Increase lockdep limits: MAX_STACK_TRACE_ENTRIES
Date: Wed, 8 Jul 2009 14:44:18 -0400 [thread overview]
Message-ID: <20090708184418.GB16090@redhat.com> (raw)
In-Reply-To: <1247078164.16156.18.camel@laptop>
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
next prev parent reply other threads:[~2009-07-08 18:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 15:25 [PATCH 1/3] Increase lockdep limits: MAX_STACK_TRACE_ENTRIES Joao Correia
2009-07-07 15:33 ` Peter Zijlstra
[not found] ` <a5d9929e0907070838q7ed3306du3bb7880e47d7207b@mail.gmail.com>
2009-07-07 15:38 ` Fwd: " Joao Correia
[not found] ` <1246981444.9777.11.camel@twins>
2009-07-07 15:50 ` Joao Correia
2009-07-07 15:55 ` Peter Zijlstra
2009-07-07 15:59 ` Joao Correia
2009-07-08 17:22 ` Dave Jones
2009-07-08 18:36 ` Peter Zijlstra
2009-07-08 18:44 ` Dave Jones [this message]
2009-07-08 19:48 ` Joao Correia
2009-07-08 19:56 ` Peter Zijlstra
2009-07-09 4:39 ` Dave Jones
2009-07-09 8:02 ` Peter Zijlstra
2009-07-09 16:10 ` Dave Jones
2009-07-09 17:07 ` Peter Zijlstra
2009-07-10 15:50 ` Joao Correia
2009-07-09 9:06 ` Catalin Marinas
2009-07-09 9:09 ` Peter Zijlstra
2009-07-20 13:31 ` [PATCH] lockdep: fixup stacktrace wastage Peter Zijlstra
2009-08-02 13:14 ` [tip:core/locking] lockdep: Fix backtraces tip-bot for Peter Zijlstra
2009-08-02 13:51 ` tip-bot for Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090708184418.GB16090@redhat.com \
--to=davej@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=arjan@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=fweisbec@gmail.com \
--cc=joaomiguelcorreia@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox