From: Sebastian Riemer <sebastian.riemer@profitbricks.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Reason for md raid 01 blksize limited to 4 KiB?
Date: Thu, 31 May 2012 12:26:50 +0200 [thread overview]
Message-ID: <4FC7476A.2020505@profitbricks.com> (raw)
In-Reply-To: <20120531154256.6eb567c7@notabene.brown>
On 31/05/12 07:42, NeilBrown wrote:
> Hmmm... that's bad. Looks like I have a bug .... yes I do. Patch below
> fixes it. If you could test and confirm I would appreciated it.
I've tested the patch and I can confirm that it works as expected, now.
Thanks for fixing it that fast!
I've tested at least raid 01.
How could one test the raid10.c changes? Create raid 010 where raid0.c
is below rai10.c in the stack?
> As for the cached writes being always 4K - are you writing through a
> filesystem or directly to /dev/md300??
I've got a file copy test which creates a file with fio, random data and
direct IO on ext4. Afterwards I copy the file which isn't in the cache
and measure the time. So this reads first and then writes back. During
the copy I run blktrace in order to have a closer look at the request
sizes. The throughput is at a stable number after multiple cycles.
Cheers,
Sebastian
prev parent reply other threads:[~2012-05-31 10:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 8:43 Reason for md raid 01 blksize limited to 4 KiB? Sebastian Riemer
2012-05-21 23:14 ` Stan Hoeppner
2012-05-21 23:28 ` NeilBrown
2012-05-25 12:35 ` Sebastian Riemer
2012-05-28 4:05 ` NeilBrown
2012-05-29 9:30 ` Sebastian Riemer
2012-05-29 10:25 ` NeilBrown
2012-05-30 13:03 ` Sebastian Riemer
2012-05-31 5:42 ` NeilBrown
2012-05-31 6:18 ` Yuanhan Liu
2012-05-31 10:26 ` Sebastian Riemer [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=4FC7476A.2020505@profitbricks.com \
--to=sebastian.riemer@profitbricks.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).