linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: New RAID-6 snapshot
Date: Tue, 30 Dec 2003 10:51:10 -0800	[thread overview]
Message-ID: <3FF1C91E.4090600@zytor.com> (raw)
In-Reply-To: <20031230184336.GU1882@matchmail.com>

Mike Fedyk wrote:
> 
> Does that mean that RRW (as the name seems to imply) would need to read the
> entire stripe before it could write back the updated stripe compared to a
> partial read with RMW? 
 >

Sort of.  If you have, say, seven drives total: D D D D D P Q, the 
access pattern look like:

D D D D D P Q
     ^
     Write this drive

... then RCW needs to read:

D D - D D - -

... and RMW needs to read:

- - D - - P Q


Now, if this is a "small" write (smaller than a page) then the stripe 
being modified always needs to be written, which helps RMW.  On the 
other hands, large writes really help RCW:

D D D D D P Q
^^^^^^^
Write these four drives

... then RCW only needs to read one drive, whereas RMW needs to read six.

Now, you'd never use RMW only; it's only used when it should be faster 
than RCW, which is why I'm a bit surprised about the performance 
degradation.  With only six drives in my test system it's pretty clear 
that RMW should very rarely be invoked, however, the performance ought 
to have stayed the same rather than slip.

	-hpa


  reply	other threads:[~2003-12-30 18:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-30 11:34 New RAID-6 snapshot H. Peter Anvin
2003-12-30 17:24 ` Mike Fedyk
2003-12-30 18:35   ` H. Peter Anvin
2003-12-30 18:43     ` Mike Fedyk
2003-12-30 18:51       ` H. Peter Anvin [this message]
2003-12-30 18:58         ` Mike Fedyk
2003-12-30 19:22           ` H. Peter Anvin

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=3FF1C91E.4090600@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mfedyk@matchmail.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).