From: J Sloan <jjs@lexus.com>
To: rwhron@earthlink.net
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.8 final - another data point
Date: Tue, 16 Apr 2002 11:31:15 -0700 [thread overview]
Message-ID: <3CBC6DF3.8080706@lexus.com> (raw)
In-Reply-To: <20020416084223.A1817@rushmore>
rwhron@earthlink.net wrote:
>Running dbench 128 on ext2 mounted with delalloc and Andrew's
>patches from http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.8/
>was 7.5x faster than 2.5.8 vanilla and 1.5x faster than
>2.4.19pre6aa1.
>
Wow, good stuff - I'll have to pull those down
and give it a go - looks like that light is closer
than I thought :-)
Once tux is ported to 2.5 I'll really be a happy
camper.
Joe
next prev parent reply other threads:[~2002-04-16 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 12:42 2.5.8 final - another data point rwhron
2002-04-16 18:31 ` J Sloan [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-16 21:48 rwhron
2002-04-16 22:02 ` Andrew Morton
2002-04-14 21:06 2.5.8 final - J Sloan
2002-04-15 5:46 ` 2.5.8 final - another data point J Sloan
2002-04-15 6:35 ` J Sloan
2002-04-15 7:27 ` Andrew Morton
2002-04-15 8:02 ` J Sloan
2002-04-15 7:18 ` Andrew Morton
2002-04-15 8:14 ` J Sloan
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=3CBC6DF3.8080706@lexus.com \
--to=jjs@lexus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rwhron@earthlink.net \
/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