From: Robert Love <rml@tech9.net>
To: Hugh Dickins <hugh@veritas.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Andi Kleen <ak@suse.de>, Daniel Ritz <daniel.ritz@gmx.ch>,
linux-kernel@vger.kernel.org, daniel.ritz@alcatel.ch
Subject: Re: [PATCH 2.5] speedup kallsyms_lookup
Date: 10 Jan 2003 12:15:17 -0500 [thread overview]
Message-ID: <1042218917.722.15.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.44.0301101628460.1434-100000@localhost.localdomain>
On Fri, 2003-01-10 at 11:34, Hugh Dickins wrote:
> Indeed! I think that was Andi volunteering :-}
> But we should let rml defend his wchan.
Well, of course I want to keep it - but I am biased :)
I think its a simple export that gives us a neat feature. Additionally,
from the procps perspective, it saves us from having to parse System.map
for each process. In fact, it means we do not need a System.map at all
for any procps functionality.
I guess Linus at least mildly liked it too, since he merged it.
But if its such a performance crippling item perhaps it does need to be
removed (or somehow restricted).
I do agree that, if possible, wchan should be kept simple... so, is
everyone else for the removal of /proc/pid/wchan ? :-(
Robert Love
next prev parent reply other threads:[~2003-01-10 17:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 9:53 [PATCH 2.5] speedup kallsyms_lookup Daniel Ritz
2003-01-10 15:29 ` Hugh Dickins
2003-01-10 16:03 ` William Lee Irwin III
2003-01-10 16:12 ` Andi Kleen
2003-01-10 16:13 ` William Lee Irwin III
2003-01-10 16:34 ` Hugh Dickins
2003-01-10 17:15 ` Robert Love [this message]
2003-01-10 19:44 ` Daniel Ritz
2003-01-10 16:37 ` Zwane Mwaikambo
2003-01-10 17:13 ` Valdis.Kletnieks
2003-01-10 17:19 ` Andi Kleen
2003-01-10 19:01 ` Randy.Dunlap
2003-01-11 4:28 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2003-01-11 4:14 Albert D. Cahalan
2003-01-11 5:33 ` William Lee Irwin III
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=1042218917.722.15.camel@phantasy \
--to=rml@tech9.net \
--cc=ak@suse.de \
--cc=daniel.ritz@alcatel.ch \
--cc=daniel.ritz@gmx.ch \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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 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.