From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Yong Zhang <yong.zhang0@gmail.com>
Cc: Juri Lelli <juri.lelli@gmail.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: lock_stat &rq->lock/1 class name meaning
Date: Thu, 12 May 2011 22:22:57 +0800 [thread overview]
Message-ID: <BANLkTim1pGQvGwvM09C0LCkYwmDP3uFB2Q@mail.gmail.com> (raw)
In-Reply-To: <20110512122658.GB3639@zhy>
On Thu, May 12, 2011 at 8:26 PM, Yong Zhang <yong.zhang0@gmail.com> wrote:
> On Thu, May 12, 2011 at 02:11:02PM +0200, Juri Lelli wrote:
>> Thanks!
>>
>> On 05/12/2011 12:57 PM, Yong Zhang wrote:
>> >On Wed, May 11, 2011 at 06:26:10PM +0200, Juri Lelli wrote:
>> >>Hi,
>> >>I'm trying to collect contention statistics through /proc/lock_stat
>> >>about scheduler data structures.
>> >>
>> >>What I obtain if a do "cat /proc/lock_stat" is something like:
>> >>...
>> >>&rq->lock: 13128 13128 0.43
>> >>[...]
>> >>
>> >>I guess the first one is about the per-rq (per-CPU) spinlock, but
>> >>what about the second? What the "/1" stands for?
>> >
>> >It is also rq but it's subclass is 1.
>> >
>> >Take a look at raw_spin_lock_nested(&this_rq->lock, SINGLE_DEPTH_NESTING);
>> >in _double_lock_balance()
>>
>> Ok, I've put more light on this also looking at lockdep.h comments
>> and lockdep-design documentation.
>>
>> Since I'm probably not the only one having troubles undestanding
>> lock_stat output, maybe could be useful to add something on this
>> inside lockstat documentation (I can try to do this). What you
>> think?
>
> Any improvement will be good :)
I think Documentation/lockstat.txt is out of date,
the last change of this file can be back to
Thu Nov 19 13:54:05 2009.
prev parent reply other threads:[~2011-05-12 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 16:26 Juri Lelli
2011-05-12 10:57 ` Yong Zhang
2011-05-12 12:11 ` Juri Lelli
2011-05-12 12:26 ` Yong Zhang
2011-05-12 14:22 ` Américo Wang [this message]
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=BANLkTim1pGQvGwvM09C0LCkYwmDP3uFB2Q@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yong.zhang0@gmail.com \
/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
Powered by JetHome