From: Neil Brown <neilb@suse.de>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
linux-ext4@vger.kernel.org, Alan Piszcz <ap@solarrain.com>
Subject: Re: mdadm software raid + ext4, capped at ~350MiB/s limitation/bug?
Date: Sun, 28 Feb 2010 08:01:00 +1100 [thread overview]
Message-ID: <20100228080100.092c24c2@notabene.brown> (raw)
In-Reply-To: <alpine.DEB.2.00.1002270840410.27192@p34.internal.lan>
On Sat, 27 Feb 2010 08:47:48 -0500 (EST)
Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
> Hello,
>
> I have two separate systems and with ext4 I cannot get speeds greater than
> ~350MiB/s when using ext4 as the filesystem on top of a raid5 or raid0.
> It appears to be a bug with ext4 (or its just that ext4 is slower for this
> test)?
>
> Each system runs 2.6.33 x86_64.
Could be related to the recent implementation of IO barriers in md.
Can you try mounting your filesystem with
-o barrier=0
and see how that changes the result.
NeilBrown
>
> Can someone please confirm?
>
> Here is ext4:
>
> # dd if=/dev/zero of=bigfile bs=1M count=10240
> 10240+0 records in
> 10240+0 records out
> 10737418240 bytes (11 GB) copied, 29.8556 s, 360 MB/s
>
> The result is the same regardless of the RAID type (RAID-5 or RAID-0)
>
> Note, this is not a bandwidth problem:
>
> # dd if=/dev/zero of=/dev/md0 bs=1M count=10240
> 10240+0 records in
> 10240+0 records out
> 10737418240 bytes (11 GB) copied, 17.6871 s, 607 MB/s
>
> With XFS:
>
> p63:~# mkfs.xfs -f /dev/md0
> p63:~# mount /dev/md0 /r1
> p63:~# cd /r1
> 10240+0 records in
> 10240+0 records out
> 10737418240 bytes (11 GB) copied, 17.6078 s, 610 MB/s
>
> NOTE: With a HW raid controller (OR using XFS), I can get > 500 MiB/s,
> this problem only occurs with SW raid (Linux/mdadm).
>
> Example (3ware 9650SE-16PML RAID-6, 15 drives (using EXT4)
> $ dd if=/dev/zero of=bigfile bs=1M count=10240
> 10240+0 records in
> 10240+0 records out
> 10737418240 bytes (11 GB) copied, 21.1729 s, 507 MB/s
>
> Justin.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" 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:[~2010-02-27 21:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 13:47 mdadm software raid + ext4, capped at ~350MiB/s limitation/bug? Justin Piszcz
2010-02-27 21:01 ` Neil Brown [this message]
2010-02-27 21:30 ` Justin Piszcz
2010-02-28 0:09 ` Bill Davidsen
2010-02-28 9:45 ` Justin Piszcz
2010-02-28 14:26 ` Bill Davidsen
2010-02-28 15:00 ` Justin Piszcz
2010-02-28 14:33 ` Mike Snitzer
2010-02-28 14:33 ` Mike Snitzer
2010-02-28 15:03 ` Justin Piszcz
2010-02-28 15:36 ` Bill Davidsen
2010-02-28 20:03 ` Justin Piszcz
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=20100228080100.092c24c2@notabene.brown \
--to=neilb@suse.de \
--cc=ap@solarrain.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.