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:35:53 -0800	[thread overview]
Message-ID: <3FF1C589.3070906@zytor.com> (raw)
In-Reply-To: <20031230172420.GS1882@matchmail.com>

Mike Fedyk wrote:
> On Tue, Dec 30, 2003 at 03:34:28AM -0800, H. Peter Anvin wrote:
> 
>>Well, I implemented read-modify-write for RAID-6, and at least on my
>>6-disk system it was a small but measurable performance *loss*.
> 
> What was your previous patch doing instead?

The published snapshots (including the latest, since I backed out 
read-modify-write) all do read-reconstruct-write.

	-hpa


  reply	other threads:[~2003-12-30 18:35 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 [this message]
2003-12-30 18:43     ` Mike Fedyk
2003-12-30 18:51       ` H. Peter Anvin
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=3FF1C589.3070906@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).