public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Valdis.Kletnieks@vt.edu, Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.5] speedup kallsyms_lookup
Date: Fri, 10 Jan 2003 18:19:50 +0100	[thread overview]
Message-ID: <20030110171950.GA6064@wotan.suse.de> (raw)
In-Reply-To: <200301101713.h0AHDmLK010383@turing-police.cc.vt.edu>

On Fri, Jan 10, 2003 at 12:13:48PM -0500, Valdis.Kletnieks@vt.edu wrote:
> On Fri, 10 Jan 2003 17:12:12 +0100, Andi Kleen <ak@suse.de>  said:
> > 
> > > So the end-result of the discussion is, "What should really happen here?"
> > > and "What, if anything, do you want me to do?"
> > 
> > IMHO best would be to get rid of /proc/*/wchan and keep the kallsyms 
> > lookup slow, simple and stupid.
> 
> And replace the current /proc/*/wchan functionality with what?

Ctrl-Rollen (or whatever the key is called on your keyboard) on the console,
like in all previous linux releases.

Note /proc/*/wchan is not in 2.4.

Also you still have WCHAN in ps, just not a full backtrace.

-Andi

  reply	other threads:[~2003-01-10 17:11 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
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 [this message]
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=20030110171950.GA6064@wotan.suse.de \
    --to=ak@suse.de \
    --cc=Valdis.Kletnieks@vt.edu \
    --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