From: rwhron@earthlink.net
To: jmorris@intercode.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: Performance issue in 2.5.32+
Date: Sun, 8 Sep 2002 09:19:51 -0400 [thread overview]
Message-ID: <20020908131951.GA25301@rushmore> (raw)
> lmbench shows major changes in context switching latencies
> on a dual celeron system
Some lmbench tests vary a lot so I run it 25 times and
average the results. Some variations are only apparent on
particular cpus (cache size differences, smp, etc).
The lmbench averaging script I use is:
http://home.earthlink.net/~rwhron/kernel/lmbsum
lmbench on a quad xeon and a bit on how to use lmbsum:
http://home.earthlink.net/~rwhron/kernel/bigbox.html#lmbench
Recent uniprocessor results:
http://home.earthlink.net/~rwhron/kernel/latest.html#lmbench
--
Randy Hron
http://home.earthlink.net/~rwhron/kernel/bigbox.html
next reply other threads:[~2002-09-08 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-08 13:19 rwhron [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-08 11:46 Performance issue in 2.5.32+ James Morris
2002-09-08 11:57 ` Andi Kleen
2002-09-08 12:55 ` James Morris
2002-09-08 15:45 ` Linus Torvalds
2002-09-08 17:40 ` James Morris
2002-09-08 18:09 ` Linus Torvalds
2002-09-09 16:06 ` James Morris
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=20020908131951.GA25301@rushmore \
--to=rwhron@earthlink.net \
--cc=jmorris@intercode.com.au \
--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