From: rwhron@earthlink.net
To: linux-kernel@vger.kernel.org
Cc: akpm@zip.com.au
Subject: Re: [patch] delayed disk block allocation
Date: Mon, 4 Mar 2002 09:54:50 -0500 [thread overview]
Message-ID: <20020304145450.GA14256@rushmore> (raw)
It's not on a big box, but I have a side by side of
2.5.6-pre2 and 2.5.6-pre2 with patches from
http://www.zipworld.com.au/~akpm/linux/patches/2.5/2.5.6-pre2/
2.5.6-pre2-akpm compiled with MPIO_DEBUG = 0 and ext2
filesystem mounted with delalloc.
tiobench and dbench were on ext2.
bonnie++ and most other tests were on reiserfs.
2.5.6-pre2-akpm throughput on ext2 is much improved.
http://home.earthlink.net/~rwhron/kernel/akpm.html
One odd number in lmbench is page fault latency. Lmbench also
showed high page fault latency in 2.4.18-pre9 with make_request,
read-latency2, and low-latency. 2.4.19-pre1aa1 with read_latency2
(2.4.19pre1aa1rl) did not show a bump in page fault latency.
--
Randy Hron
next reply other threads:[~2002-03-04 14:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 14:54 rwhron [this message]
2002-03-04 15:10 ` [patch] delayed disk block allocation Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2002-03-07 12:06 Etienne Lorrain
2002-03-07 14:47 ` Steve Lord
2002-03-07 17:30 ` Mike Fedyk
2002-03-01 8:26 Andrew Morton
2002-03-04 2:08 ` Daniel Phillips
2002-03-04 3:10 ` Jeff Garzik
2002-03-04 7:27 ` Andrew Morton
2002-03-04 5:04 ` Mike Fedyk
2002-03-04 5:31 ` Andreas Dilger
2002-03-04 5:40 ` Mike Fedyk
2002-03-04 6:14 ` Andreas Dilger
2002-03-04 5:41 ` Jeff Garzik
2002-03-04 6:18 ` Andreas Dilger
2002-03-04 15:02 ` Hans Reiser
2002-03-06 12:59 ` Pavel Machek
2002-03-04 7:53 ` Andrew Morton
2002-03-04 8:06 ` Daniel Phillips
2002-03-04 8:34 ` Andrew Morton
2002-03-04 7:20 ` Andrew Morton
2002-03-04 9:23 ` Daniel Phillips
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=20020304145450.GA14256@rushmore \
--to=rwhron@earthlink.net \
--cc=akpm@zip.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