mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@grupopie.com>
To: Robin Holt <holt@sgi.com>
Cc: jmerkey@comcast.net, linux-kernel@vger.kernel.org, jmerkey@drdos.com
Subject: Re: kallsyms 2.6.8 address ordering
Date: Fri, 20 Aug 2004 12:42:46 +0100	[thread overview]
Message-ID: <4125E3B6.6090406@grupopie.com> (raw)
In-Reply-To: <20040819190029.GC1313@lnx-holt.americas.sgi.com>

Robin Holt wrote:
>....
> 
> It must be useful for people using small memory footprint machines.
> Check with the folks doing embedded stuff.
> 
> I remember a discussion about kallsyms and scaling problems with
> top reading some /proc/<pid> file.
> 
> Look at this:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=108758995727517&w=2
> 

I posted recently (exactly one week ago) a different approach to this 
problem that increased kallsyms_lookup performance about 100 times, 
without a cache and without locking.

The patch is currently in Ingo Molnar's tree (I think). It works by 
doing binary search on tha address table and then using pre-calculated 
markers on the stem stream to search closer to the target. After that it 
copies only the stems before the searched symbol that actually 
contribute to the final result.

You can check the thread here:

http://marc.theaimsgroup.com/?l=linux-kernel&m=109245918613781&w=2

(Please note that the original patch broke handling of aliased symbols 
which was corrected later in the thread)

I'm working on an even better approach right now and I should have a 
patch ready this weekend.

This however has nothing to do with _module_ symbol names, which is a 
different problem altogether.

-- 
Paulo Marques - www.grupopie.com

  reply	other threads:[~2004-08-20 11:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19 18:10 jmerkey
2004-08-19 18:19 ` Christoph Hellwig
2004-08-19 18:30 ` Rik van Riel
2004-08-19 18:40 ` Richard B. Johnson
2004-08-19 19:00 ` Robin Holt
2004-08-20 11:42   ` Paulo Marques [this message]
2004-08-19 20:10 ` Horst von Brand
2004-08-19 18:26 jmerkey
2004-08-19 18:33 ` Christoph Hellwig
2004-08-19 19:14 jmerkey
2004-08-19 19:22 jmerkey
2004-08-19 19:24 jmerkey
2004-08-19 19:27 jmerkey
2004-08-19 19:42 ` David S. Miller
2004-08-19 22:07   ` Julien Oster
2004-08-19 22:40 jmerkey
2004-08-19 23:11 ` Francois Romieu
2004-08-19 22:43 jmerkey
2004-08-20  1:23 ` Horst von Brand

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=4125E3B6.6090406@grupopie.com \
    --to=pmarques@grupopie.com \
    --cc=holt@sgi.com \
    --cc=jmerkey@comcast.net \
    --cc=jmerkey@drdos.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