From: Miquel van Smoorenburg <mikevs@xs4all.net>
To: stan@hardwarefreak.com
Cc: David Brown <david.brown@hesbynett.no>,
Michael Tokarev <mjt@tls.msk.ru>,
Linux RAID <linux-raid@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: O_DIRECT to md raid 6 is slow
Date: Tue, 21 Aug 2012 16:51:23 +0200 [thread overview]
Message-ID: <5033A06B.30508@xs4all.net> (raw)
In-Reply-To: <50317804.9010701@hardwarefreak.com>
On 08/20/2012 01:34 AM, Stan Hoeppner wrote:
> I'm glad you jumped in David. You made a critical statement of fact
> below which clears some things up. If you had stated it early on,
> before Miquel stole the thread and moved it to LKML proper, it would
> have short circuited a lot of this discussion. Which is:
I'm sorry about that, that's because of the software that I use to
follow most mailinglist. I didn't notice that the discussion was cc'ed
to both lkml and l-r. I should fix that.
> Thus my original statement was correct, or at least half correct[1], as
> it pertained to md/RAID6. Then Miquel switched the discussion to
> md/RAID5 and stated I was all wet. I wasn't, and neither was Dave
> Chinner. I was simply unaware of this md/RAID5 single block write RMW
> shortcut
Well, all I tried to say is that a small write of, say, 4K, to a
raid5/raid6 array does not need to re-write the whole stripe (i.e.
chunksize * nr_disks) but just 4K * nr_disks, or the RMW variant of that.
Mike.
next prev parent reply other threads:[~2012-08-21 14:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 0:49 O_DIRECT to md raid 6 is slow Andy Lutomirski
2012-08-15 1:07 ` kedacomkernel
2012-08-15 1:07 ` kedacomkernel
2012-08-15 1:12 ` Andy Lutomirski
2012-08-15 1:23 ` kedacomkernel
2012-08-15 1:23 ` kedacomkernel
2012-08-15 11:50 ` John Robinson
2012-08-15 17:57 ` Andy Lutomirski
2012-08-15 22:00 ` Stan Hoeppner
2012-08-15 22:10 ` Andy Lutomirski
2012-08-15 23:50 ` Stan Hoeppner
2012-08-16 1:08 ` Andy Lutomirski
2012-08-16 6:41 ` Roman Mamedov
2012-08-15 23:07 ` Miquel van Smoorenburg
2012-08-16 11:05 ` Stan Hoeppner
2012-08-16 21:50 ` Miquel van Smoorenburg
2012-08-17 7:31 ` Stan Hoeppner
2012-08-17 11:16 ` Miquel van Smoorenburg
2012-08-18 5:09 ` Stan Hoeppner
2012-08-18 10:08 ` Michael Tokarev
2012-08-19 3:17 ` Stan Hoeppner
2012-08-19 14:01 ` David Brown
2012-08-19 23:34 ` Stan Hoeppner
2012-08-20 0:01 ` NeilBrown
2012-08-20 4:44 ` Stan Hoeppner
2012-08-20 5:19 ` Dave Chinner
2012-08-20 5:42 ` Stan Hoeppner
2012-08-20 7:47 ` David Brown
2012-08-21 14:51 ` Miquel van Smoorenburg [this message]
2012-08-22 3:59 ` Stan Hoeppner
2012-08-19 17:02 ` Chris Murphy
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=5033A06B.30508@xs4all.net \
--to=mikevs@xs4all.net \
--cc=david.brown@hesbynett.no \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=stan@hardwarefreak.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 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.