From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Larry McVoy <lm@bitmover.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lmbench results for 2.4 and 2.5 -- updated results
Date: Mon, 24 Mar 2003 17:19:50 -0500 [thread overview]
Message-ID: <3E7F8486.8000008@nortelnetworks.com> (raw)
In-Reply-To: 20030324220435.GA11421@work.bitmover.com
Larry McVoy wrote:
> 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
Why the difference? Is it being scheduled out? Should lmbench be (optionally)
putting itself into a realtime scheduling class?
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2003-03-24 22:08 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
2003-03-24 22:04 ` Martin J. Bligh
2003-03-24 22:23 ` Larry McVoy
2003-03-24 22:19 ` Chris Friesen [this message]
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=3E7F8486.8000008@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.