From: Roland Dreier <roland@kernel.org>
To: "Maucci, Cyrille" <cyrille.maucci@hp.com>
Cc: "linux-perf-users@vger.kernel.org" <linux-perf-users@vger.kernel.org>
Subject: Re: perf for analyzing userspace contention
Date: Fri, 14 Oct 2011 00:21:06 -0700 [thread overview]
Message-ID: <CAG4TOxPYjOxojTAti7gxrPJinKkGJXTMvAYoeD5MkgQFqVmgLw@mail.gmail.com> (raw)
In-Reply-To: <0E02F16954AF394BB163AEE50FDF5485690C6533A3@GVW1121EXC.americas.hpqcorp.net>
On Thu, Oct 13, 2011 at 11:58 PM, Maucci, Cyrille <cyrille.maucci@hp.com> wrote:
> So are those mutexes acquired/released from different call sites or from one single generic function of yours like LOCK/UNLOCK and the mutex is passed as a param?
I have lots of code paths taking lots of different classes of locks.
My problem is I don't know what to ask perf for to see if I have a mutex that
is heavily contended, and so some threads are spending a lot of time asleep
waiting to acquire it. As I said, this is probably pretty basic
stuff, but I'm not
usually much of a userspace guy...
Thanks,
Roland
next prev parent reply other threads:[~2011-10-14 7:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 6:36 perf for analyzing userspace contention Roland Dreier
2011-10-14 6:58 ` Maucci, Cyrille
2011-10-14 7:21 ` Roland Dreier [this message]
2011-10-14 7:33 ` Maucci, Cyrille
2011-10-14 9:42 ` Stefan Hajnoczi
2011-10-14 16:58 ` Roland Dreier
2011-10-14 21:25 ` David Ahern
2011-10-14 22:43 ` Arnaldo Carvalho de Melo
2011-10-17 23:43 ` Arun Sharma
2011-10-18 0:12 ` David Ahern
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=CAG4TOxPYjOxojTAti7gxrPJinKkGJXTMvAYoeD5MkgQFqVmgLw@mail.gmail.com \
--to=roland@kernel.org \
--cc=cyrille.maucci@hp.com \
--cc=linux-perf-users@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).