From: Sujith Manoharan <sujith@msujith.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf lock usage
Date: Wed, 29 Jan 2014 19:23:57 +0530 [thread overview]
Message-ID: <21225.2037.467035.833797@gargle.gargle.HOWL> (raw)
In-Reply-To: <20140128093542.GD1229@krava.brq.redhat.com>
Jiri Olsa wrote:
> some of the kernel lock types do not follow the:
> acquire
> contended
> acuired
> release
>
> lock state machine, like rcu or spin locks.. and thats what
> caused most of the bad rates in my tests.
>
> I was recently working on some changes for lock tracing,
> what stats are you interested in?
I am trying to see lock usage stats for the ath9k wireless driver.
Mainly in the transmission path, where normal spin locks
are acquired.
Sujith
next prev parent reply other threads:[~2014-01-29 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 6:49 perf lock usage Sujith Manoharan
2014-01-23 12:36 ` Frederic Weisbecker
2014-01-23 12:37 ` Sujith Manoharan
2014-01-28 9:35 ` Jiri Olsa
2014-01-29 13:53 ` Sujith Manoharan [this message]
2014-01-30 10:33 ` Jiri Olsa
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=21225.2037.467035.833797@gargle.gargle.HOWL \
--to=sujith@msujith.org \
--cc=jolsa@redhat.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).