From: Rick Jones <rick.jones2@hpe.com>
To: M Kelly <mark.kelly@lexisnexis.com>, linux-perf-users@vger.kernel.org
Subject: Re: spin_lock cause ?
Date: Wed, 1 Jun 2016 13:24:31 -0700 [thread overview]
Message-ID: <574F447F.1000503@hpe.com> (raw)
In-Reply-To: <loom.20160601T211807-101@post.gmane.org>
On 06/01/2016 12:25 PM, M Kelly wrote:
> I think I recall you from hp, years ago when I was there :-)
> Thanks for the info. I suspect we are too heavy on
> pthread_mutex_lock()/unlock()
HP-UX has some ways/tools to track mutex contention. Some extensions to
give names to mutexes and then get stats on how often one went to grab
them and it was held etc etc. Been ages since I used them - I'd hope
there was something similar for Linux but I've not played with threads
in a very long time.
happy benchmarking,
rick jones
next prev parent reply other threads:[~2016-06-01 20:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 17:05 spin_lock cause ? Kelly, Mark (RIS-BCT)
2016-06-01 17:37 ` Milian Wolff
2016-06-01 17:43 ` M Kelly
2016-06-01 18:11 ` Arnaldo Carvalho de Melo
2016-06-01 18:49 ` M Kelly
2016-06-01 18:53 ` Rick Jones
2016-06-01 19:25 ` M Kelly
2016-06-01 20:24 ` Rick Jones [this message]
2016-06-01 21:10 ` David Ahern
2016-06-02 9:18 ` Milian Wolff
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=574F447F.1000503@hpe.com \
--to=rick.jones2@hpe.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.kelly@lexisnexis.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;
as well as URLs for NNTP newsgroup(s).