From: Bill Huey (hui) <billh@gnuppy.monkey.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: linux-kernel@vger.kernel.org, Jason Baron <jbaron@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
"Bill Huey (hui)" <billh@gnuppy.monkey.org>
Subject: Re: [PATCH] lockdep: lock contention tracking
Date: Sun, 20 May 2007 23:04:46 -0700 [thread overview]
Message-ID: <20070521060446.GA4593@gnuppy.monkey.org> (raw)
In-Reply-To: <1179657026.5915.10.camel@lappy>
On Sun, May 20, 2007 at 12:30:26PM +0200, Peter Zijlstra wrote:
> The 4 points are the first 4 unique callsites that cause lock contention
> for the specified lock class.
>
> writing a 0 to /proc/lockdep_contentions clears the stats
We should talk about unifying it with my lockstat work for -rt so that
we have a comprehensive solution for the "world". But you know that
already :)
Unifying lock initializer hash key initialization functions is a key
first step to that. Keep in mind, we can do more with this mechanism
than just kernel locks and we should probably keep that open and not
code into a corner.
bill
next prev parent reply other threads:[~2007-05-21 6:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 10:30 [PATCH] lockdep: lock contention tracking Peter Zijlstra
2007-05-20 18:05 ` Ingo Molnar
2007-05-21 6:04 ` Bill Huey [this message]
2007-05-21 6:08 ` Ingo Molnar
2007-05-21 6:41 ` Bill Huey
2007-05-21 7:50 ` Ingo Molnar
2007-05-21 9:18 ` Bill Huey
2007-05-21 9:36 ` Ingo Molnar
2007-05-21 9:55 ` Christoph Hellwig
2007-05-21 10:21 ` Bill Huey
2007-05-21 10:58 ` Ingo Molnar
2007-05-21 19:17 ` Bill Huey
2007-05-21 10:19 ` Bill Huey
2007-05-21 10:28 ` Bill Huey
2007-05-21 12:46 ` Ingo Molnar
2007-05-21 19:09 ` Bill Huey
2007-05-21 20:58 ` Jason Baron
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=20070521060446.GA4593@gnuppy.monkey.org \
--to=billh@gnuppy.monkey.org \
--cc=a.p.zijlstra@chello.nl \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
/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