From: Roland Dreier <rdreier@cisco.com>
To: Jason Baron <jbaron@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, arjan@infradead.org
Subject: Re: locking hierarchy based on lockdep
Date: Mon, 06 Nov 2006 12:37:56 -0800 [thread overview]
Message-ID: <ada8xiol3a3.fsf@cisco.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611061519220.29750@dhcp83-20.boston.redhat.com> (Jason Baron's message of "Mon, 6 Nov 2006 15:22:33 -0500 (EST)")
> 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.
next prev parent reply other threads:[~2006-11-06 20:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 18:32 locking hierarchy based on lockdep Jason Baron
2006-11-06 20:05 ` Ingo Molnar
2006-11-06 20:21 ` Roland Dreier
2006-11-06 20:22 ` Jason Baron
2006-11-06 20:37 ` Roland Dreier [this message]
2006-11-06 20:40 ` Jason Baron
2006-11-07 23:39 ` Jason Baron
2006-11-07 23:53 ` Ingo Molnar
2006-11-08 18:04 ` Jason Baron
2006-11-09 9:15 ` Ingo Molnar
2006-11-09 18:58 ` Jason Baron
2006-11-10 9:27 ` Ingo Molnar
2006-11-08 13:08 ` Pavel Machek
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=ada8xiol3a3.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=arjan@infradead.org \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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