[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4840297C.7030809@bull.net>
Date: Fri, 30 May 2008 18:21:16 +0200
From: Valerie Clement <valerie.clement@...l.net>
To: Eric Sandeen <sandeen@...hat.com>
Cc: ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: Test results for ext4
Eric Sandeen wrote:
> Valerie Clement wrote:
>> Hi all,
>>
>> Since a couple of weeks, I did batches of tests to have some performance
>> numbers for the new ext4 features like uninit_groups, flex_bg or
>> journal_checksum on a 5TB filesystem.
>> I tried to test allmost all combinations of mkfs and mount options, but
>> I put only a subset of them in the result tables, the most significant
>> for me.
>>
>> I had started to do these tests on a kernel 2.6.26-rc1, but I'd got several
>> hangs and crashes occuring randomly outside ext4, sometimes in the slab
>> code or in the scsi driver eg., and which were not reproductible.
>> Since 2.6.26-rc2, no crash or hang occur with ext4 on my system.
>>
>> The first results and the test description are available here:
>> 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
>
> To be fair in your comparisons with xfs, you should probably either turn
> barriers off for xfs, or on for ext[34], just FWIW.
>
Oops, I did the test on a device mapper /dev/md0. I forgot to change it in
the test description. I will do it.
When mounting the xfs filesystem, I've got the following message:
Filesystem "md0": Disabling barriers, not supported by the underlying device
It means barriers are not supported by my device, isn' it?
Valérie
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists