From: Peter Zijlstra <peterz@infradead.org>
To: John Kacur <jkacur@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
linux-rt-users@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Clark Williams <williams@redhat.com>,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
Gregory Haskins <ghaskins@novell.com>
Subject: Re: [PATCH v3] lockdep: Make MAX_STACK_TRACE_ENTRIES configurable.
Date: Wed, 21 Apr 2010 14:24:31 +0200 [thread overview]
Message-ID: <1271852671.1776.101.camel@laptop> (raw)
In-Reply-To: <alpine.LFD.2.00.1004211407510.4506@localhost.localdomain>
On Wed, 2010-04-21 at 14:12 +0200, John Kacur wrote:
>
> lock-classes: 1330 [max: 8191]
> direct dependencies: 12754 [max: 16384]
> indirect dependencies: 33245
> all direct dependencies: 49074
> dependency chains: 19641 [max: 32768]
Right, so each dependency also gets a stack trace, see
add_lock_to_list().
> dependency chain hlocks: 73246 [max: 163840]
> in-hardirq chains: 25
> in-softirq chains: 0
> in-process chains: 19616
> stack-trace entries: 262144 [max: 262144]
>
>
> I'm looking at more details in /proc/lockdep and friends to see if
> I can find any more details, or something that looks amiss.
>
It might be useful to add a counter that simply counts all save_trace()
invocations, and maybe split them out according to new_bit in
mark_lock().
next prev parent reply other threads:[~2010-04-21 12:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 11:45 [RFC: PATCH] lockdep: Make MAX_STACK_TRACE_ENTRIES configurable John Kacur
2010-04-16 15:29 ` [RFC: PATCH v2] " John Kacur
2010-04-19 16:51 ` John Kacur
2010-04-20 21:09 ` Andrew Morton
2010-04-21 11:12 ` [PATCH v3] " John Kacur
2010-04-21 11:37 ` Peter Zijlstra
2010-04-21 11:47 ` Gregory Haskins
2010-04-21 12:03 ` Peter Zijlstra
2010-04-21 12:12 ` John Kacur
2010-04-21 12:24 ` Peter Zijlstra [this message]
2010-04-21 14:53 ` Sven-Thorsten Dietrich
[not found] <4BCEB92D0200005A0006515F@soto.provo.novell.com>
2010-04-21 12:37 ` Gregory Haskins
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=1271852671.1776.101.camel@laptop \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=ghaskins@novell.com \
--cc=jkacur@redhat.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.