From: Milian Wolff <milian.wolff@kdab.com>
To: Mark.Kelly@lexisnexis.com
Cc: linux-perf-users@vger.kernel.org
Subject: Re: spin_lock cause ?
Date: Wed, 01 Jun 2016 19:37:51 +0200 [thread overview]
Message-ID: <4716588.WReR5L1Wkn@milian-kdab2> (raw)
In-Reply-To: <574F15E4.5070008@lexisnexis.com>
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
On Wednesday, June 1, 2016 1:05:40 PM CEST Kelly, Mark (RIS-BCT) wrote:
> Hi,
>
> Perf report for our application shows:
>
> 34.27% [kernel] [k] _spin_lock
> 8.19% libjlib.so [.] CLZWExpander::expand(void*)
> 4.62% libjhtree.so [.] CMRUCacheOf<CKeyIdAndPos,
> CJHTreeNode> 1.97% [kernel] [k] futex_wait_setup
> 1.51% [kernel] [k] native_write_msr_safe
> 1.34% [kernel] [k] futex_wake
>
> Any suggestion for how to trace where/who is responsible for the spin_lock ?
For both cases, you should collect backtraces which should allow you to find
culprits. Have you tried:
perf record --call-graph dwarf
or similar?
Cheers
--
Milian Wolff | milian.wolff@kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5903 bytes --]
next prev parent reply other threads:[~2016-06-01 17:38 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 [this message]
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
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=4716588.WReR5L1Wkn@milian-kdab2 \
--to=milian.wolff@kdab.com \
--cc=Mark.Kelly@lexisnexis.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).