From: rwhron@earthlink.net
To: akpm@digeo.com, piggin@cyberone.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.63-mm2
Date: Sun, 9 Mar 2003 12:35:51 -0500 [thread overview]
Message-ID: <20030309173551.GA3055@rushmore> (raw)
2.5.64-mm1 on K6/2 uniprocessor completed the 24 hour benchmarks
using anticipatory scheduler with no oops. (Badness in request_irq
at arch/i386/kernel/irq.c:475 is known and non-fatal).
2.5.64-mm1 had ~ 47% improvement in tiobench sequential read
throughput on ext2, compared to 2.5.64 on uniprocessor K6/2.
2.5.64-mm2 ran dbench, Linux Test Project, unixbench, lmbench
with no problems on uniprocessor too.
2.5.64-mm4 is running on Quad Xeon now, and has finished dbench
runs with no oops.
--
Randy Hron
http://home.earthlink.net/~rwhron/kernel/bigbox.html
next reply other threads:[~2003-03-09 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-09 17:35 rwhron [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-04 0:50 2.5.63-mm2 rwhron
2003-03-03 2:09 2.5.63-mm2 Andrew Morton
2003-03-04 21:57 ` 2.5.63-mm2 Mark Wong
2003-03-04 22:09 ` 2.5.63-mm2 Andrew Morton
2003-03-04 23:06 ` 2.5.63-mm2 Mark Wong
2003-03-04 23:18 ` 2.5.63-mm2 Andrew Morton
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=20030309173551.GA3055@rushmore \
--to=rwhron@earthlink.net \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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