public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: William Lee Irwin III <wli@holomorphy.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Larry McVoy <lm@bitmover.com>,
	linux-kernel@vger.kernel.org
Subject: Re: top hogs CPU in 2.6: kallsyms_lookup is very slow
Date: Fri, 17 Sep 2004 06:55:35 -0700	[thread overview]
Message-ID: <20040917135534.GA13299@work.bitmover.com> (raw)
In-Reply-To: <200409171604.39622.vda@port.imtp.ilyichevsk.odessa.ua>

> Is there an easy way to run only this one? I can profile that.
> Larry? 

Absolutely, when you are in the source directory you can see how all this
is run, it's just a shell script.  Look in ../scripts/lmbench for lat_pipe
and run that.

In general, the code in LMbench is very very small and it's easy to tinker
with the system and add more tests.  I've been very surprised over the 
years that people haven't done so.

For what it is worth, we're looking at porting LMbench to Windows using 
the Unix API layer we did in BitKeeper.  
-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com

      reply	other threads:[~2004-09-17 13:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 11:28 top hogs CPU in 2.6: kallsyms_lookup is very slow Denis Vlasenko
2004-09-16 11:45 ` William Lee Irwin III
2004-09-16 11:57   ` Denis Vlasenko
2004-09-16 12:17     ` William Lee Irwin III
2004-09-16 12:31       ` Denis Vlasenko
2004-09-17  8:57       ` Denis Vlasenko
2004-09-17 11:03         ` William Lee Irwin III
2004-09-17 12:34           ` Denis Vlasenko
2004-09-17 13:33             ` William Lee Irwin III
2004-09-17 20:36               ` Denis Vlasenko
2004-09-17 21:32                 ` William Lee Irwin III
     [not found]             ` <200409172155.29561.vda@port.imtp.ilyichevsk.odessa.ua>
2004-09-18 13:57               ` [PATCH] trivial patch for 2.4: always inline __constant_* Denis Vlasenko
2004-09-18 14:03                 ` [PATCH] trivial patch for 2.4: resolve megaraid_info name collision Denis Vlasenko
2004-09-18 14:02                   ` Marcelo Tosatti
2004-09-18 15:05                 ` [PATCH] trivial patch for 2.4: always inline __constant_* Marcelo Tosatti
2004-09-17  9:01       ` top hogs CPU in 2.6: kallsyms_lookup is very slow Denis Vlasenko
2004-09-17 10:55         ` William Lee Irwin III
2004-09-17 11:27         ` Paulo Marques
2004-09-17 11:21       ` Denis Vlasenko
2004-09-17 12:10         ` William Lee Irwin III
2004-09-17 13:04           ` Denis Vlasenko
2004-09-17 13:55             ` Larry McVoy [this message]

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=20040917135534.GA13299@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox