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, 6 Nov 2006 15:40:59 -0500 (EST)
From:	Jason Baron <jbaron@...hat.com>
To:	Roland Dreier <rdreier@...co.com>
cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	arjan@...radead.org
Subject: Re: locking hierarchy based on lockdep


On Mon, 6 Nov 2006, Roland Dreier wrote:

>  > interesting...perhaps if we layered say the directory structure on the 
>  > list too like by the top level kernel directories drivers, kernel, mm, 
>  > net, etc. it might be more readable.
> 
> I'm not sure that you need to do something manual or ad hoc like that,
> although it might be necessary in the end.  I'd be curious to see how
> the list of locks partitions up if you just divide it up into groups
> of locks that have some relationship.  I guess the question is, if you
> draw the graph whose nodes are locks and whose edges connect locks
> that are held together, how many connected pieces does that graph have?
> 
>  - R.
> 

ok, so grouping the list by sections of connected components-that's a nice 
idea, and would probably make for an interesting list.

-jason
-
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/

Powered by blists - more mailing lists