From: Valerie Clement <valerie.clement@bull.net>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: Test results for ext4
Date: Mon, 02 Jun 2008 15:07:08 +0200 [thread overview]
Message-ID: <4843F07C.5020306@bull.net> (raw)
In-Reply-To: <48402B49.7000805@redhat.com>
Eric Sandeen wrote:
> Oh, also for completeness can you specify which xfsprogs you used?
> There were some recent changes made which affect the fs geometry, and
> might affect the results. So it would be good to fully specify.
OK, to do. To be honest, I didn't update them recently.
>
> Also why no fragmentation results for xfs or ext3?
I only forgot to do it.
But I didn't want to make a full comparaison of ext4 to xfs and ext3.
When testing the latest ext4 patch queue with a new kernel, I'd got
sometimes kernel crashes, or system hang, or bad performance.
Running the same tests on ext3 and xfs for which the code is more
stable I think gives me reference numbers for my tests.
In this way, I found in the past a problem in the IO scheduler.
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
next prev parent reply other threads:[~2008-06-02 13:07 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 [this message]
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
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=4843F07C.5020306@bull.net \
--to=valerie.clement@bull.net \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/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).