mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Albert Cahalan <albert@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org, ak@suse.de, bcasavan@sgi.com
Subject: Re: [PATCH] Add kallsyms_lookup() result cache
Date: Sat, 19 Jun 2004 03:06:37 -0700	[thread overview]
Message-ID: <20040619030637.5580b25e.akpm@osdl.org> (raw)
In-Reply-To: <1087605785.8188.834.camel@cube>

Albert Cahalan <albert@users.sourceforge.net> wrote:
>
> > 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

Poll /proc/modules?

>  2. the /proc/*/wchan files don't provide both name and address

/proc/stat has the address, /proc/kallsyms gives the symbol?

>  I'd be happy to make top (and the rest of procps) use a cache
>  if those problems were addressed. I need a signal sent on
>  module load/unload, or a real /proc/kallsyms st_mtime that I
>  can poll. I also need to have the numeric wchan address in
>  the /proc/*/wchan file, such that it is reliably the same
>  thing as the function name already found there.

Updating mtime on /proc/modules may be more logical, or even both.

Or put a modprobe sequence number somewhere in /proc and look for changes
in that.

It definitely needs to be fixed, but it doesn't seem that adding code to
the kernel is needed.


  parent reply	other threads:[~2004-06-19 10:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-19  0:43 Albert Cahalan
2004-06-19  4:51 ` Herbert Xu
2004-06-19 12:03   ` Albert Cahalan
2004-06-19 10:06 ` Andrew Morton [this message]
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=20040619030637.5580b25e.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ak@suse.de \
    --cc=albert@users.sourceforge.net \
    --cc=bcasavan@sgi.com \
    --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

Powered by JetHome