public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Andrew Morton <akpm@digeo.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	lm@bitmover.com, venkatesh.pallipadi@intel.com,
	linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: lmbench results for 2.4 and 2.5 -- updated results
Date: Mon, 24 Mar 2003 14:04:35 -0800	[thread overview]
Message-ID: <20030324220435.GA11421@work.bitmover.com> (raw)
In-Reply-To: <20030324153602.28b44e23.akpm@digeo.com>

On Mon, Mar 24, 2003 at 03:36:02PM -0800, Andrew Morton wrote:
> "Martin J. Bligh" <mbligh@aracnet.com> wrote:
> >
> > On a slightly related note, I played with lmbench a bit over the weekend,
> > but the results were too unstable to be useful ... they're also too short
> > to profile ;-( 
> > 
> > I presume it does 100 iterations of a test (like fork latency?). Or does 
> > it just do one? Can I make it do 1,000,000 iterations or something
> > fairly easily ? ;-) I didn't really look closely, just apt-get install
> > lmbench ... 
> 
> Yes, that is something I've wanted several times.  Just a way to say "run
> this test for ever so I can profile the thing".
> 
> Even a sleazy environment string would suffice.

It's been there, I suppose you need to read the source to figure it out
though the lmbench script also plays with this I believe.

work ~/LMbench2/bin/i686-pc-linux-gnu ENOUGH=1000000 time bw_pipe
Pipe bandwidth: 655.37 MB/sec
real    0m23.411s
user    0m0.480s
sys     0m1.180s

work ~/LMbench2/bin/i686-pc-linux-gnu time bw_pipe
Pipe bandwidth: 809.81 MB/sec

real    0m2.821s
user    0m0.480s
sys     0m1.180s


-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm

  reply	other threads:[~2003-03-24 21:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 19:53 lmbench results for 2.4 and 2.5 -- updated results Pallipadi, Venkatesh
2003-03-24 20:01 ` Larry McVoy
2003-03-24 21:09   ` Martin J. Bligh
2003-03-24 23:36     ` Andrew Morton
2003-03-24 22:04       ` Larry McVoy [this message]
2003-03-24 22:04         ` Martin J. Bligh
2003-03-24 22:23           ` Larry McVoy
2003-03-24 22:19         ` Chris Friesen
2003-03-25 18:23         ` Martin J. Bligh
2003-03-26  1:50           ` Larry McVoy
2003-03-26  2:09             ` Martin J. Bligh
  -- strict thread matches above, loose matches on Subject: below --
2003-03-24 20:11 Nakajima, Jun
2003-03-22 16:11 lmbench results for 2.4 and 2.5 Chris Friesen
2003-03-24  6:08 ` lmbench results for 2.4 and 2.5 -- updated results Chris Friesen
2003-03-24  8:39   ` Linus Torvalds
2003-03-24  9:03     ` 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=20030324220435.GA11421@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=torvalds@transmeta.com \
    --cc=venkatesh.pallipadi@intel.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