All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kelly, Mark (RIS-BCT)" <Mark.Kelly@lexisnexis.com>
To: linux-perf-users@vger.kernel.org
Subject: spin_lock cause ?
Date: Wed, 1 Jun 2016 13:05:40 -0400	[thread overview]
Message-ID: <574F15E4.5070008@lexisnexis.com> (raw)

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 ?

thank you in advance,
mark



---------------------------------------- The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.  

             reply	other threads:[~2016-06-01 17:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-01 17:05 Kelly, Mark (RIS-BCT) [this message]
2016-06-01 17:37 ` spin_lock cause ? 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
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=574F15E4.5070008@lexisnexis.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.