From: William Lee Irwin III <wli@holomorphy.com>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Larry McVoy <lm@bitmover.com>,
viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: top hogs CPU in 2.6: kallsyms_lookup is very slow
Date: Fri, 17 Sep 2004 14:32:58 -0700 [thread overview]
Message-ID: <20040917213258.GB9106@holomorphy.com> (raw)
In-Reply-To: <200409172336.25695.vda@port.imtp.ilyichevsk.odessa.ua>
On Fri, Sep 17, 2004 at 11:36:25PM +0300, Denis Vlasenko wrote:
> Aha! Maybe it's just a might_sleep() overhead?
How does 2.6 do with those might_sleep() calls removed?
-- wli
next prev parent reply other threads:[~2004-09-17 21:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 11:28 top hogs CPU in 2.6: kallsyms_lookup is very slow Denis Vlasenko
2004-09-16 11:45 ` William Lee Irwin III
2004-09-16 11:57 ` Denis Vlasenko
2004-09-16 12:17 ` William Lee Irwin III
2004-09-16 12:31 ` Denis Vlasenko
2004-09-17 8:57 ` Denis Vlasenko
2004-09-17 11:03 ` William Lee Irwin III
2004-09-17 12:34 ` Denis Vlasenko
2004-09-17 13:33 ` William Lee Irwin III
2004-09-17 20:36 ` Denis Vlasenko
2004-09-17 21:32 ` William Lee Irwin III [this message]
[not found] ` <200409172155.29561.vda@port.imtp.ilyichevsk.odessa.ua>
2004-09-18 13:57 ` [PATCH] trivial patch for 2.4: always inline __constant_* Denis Vlasenko
2004-09-18 14:03 ` [PATCH] trivial patch for 2.4: resolve megaraid_info name collision Denis Vlasenko
2004-09-18 14:02 ` Marcelo Tosatti
2004-09-18 15:05 ` [PATCH] trivial patch for 2.4: always inline __constant_* Marcelo Tosatti
2004-09-17 9:01 ` top hogs CPU in 2.6: kallsyms_lookup is very slow Denis Vlasenko
2004-09-17 10:55 ` William Lee Irwin III
2004-09-17 11:27 ` Paulo Marques
2004-09-17 11:21 ` Denis Vlasenko
2004-09-17 12:10 ` William Lee Irwin III
2004-09-17 13:04 ` Denis Vlasenko
2004-09-17 13:55 ` Larry McVoy
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=20040917213258.GB9106@holomorphy.com \
--to=wli@holomorphy.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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