From: David Ahern <dsahern@gmail.com>
To: "J.H." <warthog9@kernel.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"hpa@kernel.org" <hpa@kernel.org>,
dgc@kernel.org, elder@kernel.org, hch@kernel.org
Subject: Re: do_raw_spin_lock using a lot of the system cpu time
Date: Mon, 07 Feb 2011 22:20:48 -0700 [thread overview]
Message-ID: <4D50D2B0.8030106@gmail.com> (raw)
In-Reply-To: <4D508BDC.1020309@kernel.org>
On 02/07/11 17:18, J.H. wrote:
> The debugging that so far is (via perf top) claims that alloc_vmap_area,
> rb_next and do_raw_spin_lock are involved in some combination, with
> do_raw_spin_lock being the item taking up 80-90% of the time that perf
> top can see.
Have you tried 'perf record -ga' to see the various paths to
_raw_spin_lock and rb_next?
David
prev parent reply other threads:[~2011-02-08 5:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 0:18 do_raw_spin_lock using a lot of the system cpu time J.H.
2011-02-08 4:30 ` Hugh Dickins
2011-02-08 5:20 ` David Ahern [this message]
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=4D50D2B0.8030106@gmail.com \
--to=dsahern@gmail.com \
--cc=dgc@kernel.org \
--cc=elder@kernel.org \
--cc=hch@kernel.org \
--cc=hpa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=warthog9@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.