From: Albert Cahalan <albert@users.sf.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
ak@suse.de, bcasavan@sgi.com
Subject: Re: [PATCH] Add kallsyms_lookup() result cache
Date: 19 Jun 2004 08:03:45 -0400 [thread overview]
Message-ID: <1087646624.8188.852.camel@cube> (raw)
In-Reply-To: <E1BbXoj-0006t2-00@gondolin.me.apana.org.au>
On Sat, 2004-06-19 at 00:51, Herbert Xu wrote:
> Albert Cahalan <albert@users.sf.net> wrote:
> >
> >> Are you saying your top reads /proc/kallsyms on each redisplay?
> >> That sounds completely wrong - it should only read the file once
> >> and cache it and then look the numbers it is reading from wchan
> >> in the cache.
> >>
> >> Doing the cache in the kernel is the wrong place. This should be fixed
> >> in user space.
> >
> > No way, because:
> >
> > 1. kernel modules may be loaded or unloaded at any time
>
> We seem to have coped alright under 2.4.
Not really. We coped alright long ago. Things were
getting worse year by year, with modules becoming
more popular and their symbols not 100% exported.
next prev parent reply other threads:[~2004-06-19 14:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 0:43 [PATCH] Add kallsyms_lookup() result cache Albert Cahalan
2004-06-19 4:51 ` Herbert Xu
2004-06-19 12:03 ` Albert Cahalan [this message]
2004-06-19 10:06 ` Andrew Morton
2004-06-19 13:05 ` Albert Cahalan
2004-06-22 19:45 ` Brent Casavant
2004-06-22 20:10 ` Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2004-06-18 20:03 Brent Casavant
2004-06-18 20:37 ` Martin Josefsson
2004-06-18 20:55 ` Brent Casavant
2004-06-18 22:03 ` Andi Kleen
2004-06-18 23:26 ` Jesse Barnes
2004-06-18 23:56 ` Andi Kleen
2004-06-19 0:16 ` Jesse Barnes
2004-06-18 23:31 ` Brent Casavant
2004-06-18 23:59 ` Andi Kleen
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=1087646624.8188.852.camel@cube \
--to=albert@users.sf.net \
--cc=ak@suse.de \
--cc=bcasavan@sgi.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@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