From: Eric Sandeen <sandeen@redhat.com>
To: Valerie Clement <valerie.clement@bull.net>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: Test results for ext4
Date: Wed, 04 Jun 2008 10:41:00 -0500 [thread overview]
Message-ID: <4846B78C.3020102@redhat.com> (raw)
In-Reply-To: <4846B5F9.8050906@bull.net>
Valerie Clement wrote:
> Eric Sandeen wrote:
>> This was with e2fsprogs-1.39 for ext3, e2fsprogs-1.40.10 for ext4, and
>> xfsprogs-2.9.8 for xfs.
> I was using xfsprogs-2.9.0, maybe too old version...
> I'm updating them and I'll run my tests again.
2.9.0 is about a year old... 2.9.5 got some defaults changes for
perfomance reasons, so it might make a difference. If kernel is
bleeding edge probably might as well use all bleeding-edge tools, too. :)
...
> I added a link to the scripts I used in the test description section in:
> http://www.bullopensource.org/ext4/20080530/ffsb-write-2.6.26-rc2.html
> http://www.bullopensource.org/ext4/20080530/ffsb-readwrite-2.6.26-rc2.html
Great, thanks! I think the hardware comparison is interesting...
-Eric
> Valérie
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-06-04 15:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 15:50 Test results for ext4 Valerie Clement
2008-05-30 16:01 ` Eric Sandeen
2008-05-30 16:21 ` Valerie Clement
2008-05-30 16:23 ` Eric Sandeen
2008-05-30 16:28 ` Eric Sandeen
2008-06-02 13:07 ` Valerie Clement
2008-05-30 17:48 ` Mingming
2008-06-02 13:29 ` Valerie Clement
2008-05-30 18:12 ` Jose R. Santos
2008-06-02 13:44 ` Valerie Clement
2008-06-02 14:44 ` Jose R. Santos
2008-05-30 20:58 ` Eric Sandeen
2008-06-02 14:51 ` Valerie Clement
2008-05-31 19:35 ` Eric Sandeen
2008-06-02 13:20 ` Valerie Clement
2008-06-03 3:14 ` Eric Sandeen
2008-06-04 15:34 ` Valerie Clement
2008-06-04 15:41 ` Eric Sandeen [this message]
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=4846B78C.3020102@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=valerie.clement@bull.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;
as well as URLs for NNTP newsgroup(s).