public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zach Brown <zach.brown@oracle.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, Bill Huey <billh@gnuppy.monkey.org>,
	Jason Baron <jbaron@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 0/6] lock contention tracking -v4
Date: Wed, 30 May 2007 10:40:25 -0700	[thread overview]
Message-ID: <20070530174025.GD5488@mami.zabbo.net> (raw)
In-Reply-To: <20070530124903.882133089@chello.nl>

On Wed, May 30, 2007 at 02:49:03PM +0200, Peter Zijlstra wrote:
> 
> Use the lockdep infrastructure to track lock contention and other lock
> statistics.

I really like the sound of this.

Has anyone given you an indication of when it might be merged?

- z

      parent reply	other threads:[~2007-05-30 17:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30 12:49 [PATCH 0/6] lock contention tracking -v4 Peter Zijlstra
2007-05-30 12:49 ` [PATCH 1/6] fix raw_spinlock_t vs lockdep Peter Zijlstra
2007-05-30 12:49 ` [PATCH 2/6] lockdep: sanitise CONFIG_PROVE_LOCKING Peter Zijlstra
2007-05-30 12:49 ` [PATCH 3/6] lockdep: reduce the ifdeffery Peter Zijlstra
2007-05-30 12:49 ` [PATCH 4/6] lockstat: core infrastructure Peter Zijlstra
2007-05-30 12:49 ` [PATCH 5/6] lockstat: human readability tweaks Peter Zijlstra
2007-05-30 19:39   ` Matthew Helsley
2007-05-31  9:17     ` Peter Zijlstra
2007-05-30 12:49 ` [PATCH 6/6] lockstat: hook into spinlock_t, rwlock_t, rwsem and mutex Peter Zijlstra
2007-05-30 13:17 ` [PATCH 0/6] lock contention tracking -v4 Ingo Molnar
2007-05-30 17:40 ` Zach Brown [this message]

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=20070530174025.GD5488@mami.zabbo.net \
    --to=zach.brown@oracle.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=billh@gnuppy.monkey.org \
    --cc=hch@infradead.org \
    --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