Date: Mon, 21 May 2007 08:08:28 +0200
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
Message-ID: <20070521060828.GB20277@elte.hu>
References: <1179657026.5915.10.camel@lappy> <20070521060446.GA4593@gnuppy.monkey.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070521060446.GA4593@gnuppy.monkey.org>
User-Agent: Mutt/1.4.2.2i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 951
Lines: 24


* 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/