mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Bill Huey <billh@gnuppy.monkey.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	linux-kernel@vger.kernel.org, Jason Baron <jbaron@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] lockdep: lock contention tracking
Date: Mon, 21 May 2007 08:08:28 +0200	[thread overview]
Message-ID: <20070521060828.GB20277@elte.hu> (raw)
In-Reply-To: <20070521060446.GA4593@gnuppy.monkey.org>


* Bill Huey <billh@gnuppy.monkey.org> wrote:

> 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 :)

To me it appears Peter's stuff is already a pretty complete solution on 
its own, and it's a whole lot simpler (and less duplicative) than your 
lockstat patch. Could you list the specific items/features that you 
think Peter's stuff doesnt have?

	Ingo

  reply	other threads:[~2007-05-21  6:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-20 10:30 Peter Zijlstra
2007-05-20 18:05 ` Ingo Molnar
2007-05-21  6:04 ` Bill Huey
2007-05-21  6:08   ` Ingo Molnar [this message]
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=20070521060828.GB20277@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=billh@gnuppy.monkey.org \
    --cc=jbaron@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®