linux-kernel - Re: [PATCH] lockdep: lock contention tracking

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 21 May 2007 08:08:28 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Bill Huey <billh@...ppy.monkey.org>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	linux-kernel@...r.kernel.org, Jason Baron <jbaron@...hat.com>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH] lockdep: lock contention tracking


* Bill Huey <billh@...ppy.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/