linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: gaetan.leurent@ens.fr (Gaëtan LEURENT)
To: linux-raid@vger.kernel.org
Subject: Raid 4/5 small writes
Date: Sun, 02 Apr 2006 17:37:22 +0200	[thread overview]
Message-ID: <qlk3bgwt2dp.fsf@clipper.ens.fr> (raw)

Hi,

I'm considering building a Raid4[#] array for my desktop and I have a
question about small writes with Raid4/Raid5: when a small part of a
block is modified, we have two options:

- read the hole stripe, compute the new checksum and write the data and
  the checksum

- read only the part of the data that will be overwritten, and the
  corresponding part of the checksum.  Since the checksum is a simple
  XOR, we have:
     New Checksum = Old Checksum XOR Old Data XOR New Data
  and we can write the new data and the new checksum without reading
  more data.

Does the Linux kernel implements the second way?


[#] I'm not doing Raid5 because I have two 120Go drives and two 250Go
    drives.  I am thinking of making a Raid0 array out of the two small
    drives, and using that as the parity drive for the Raid4.  I believe
    this should give better performance than Raid5.

Thanks,

-- 
Gaëtan LEURENT
-
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

             reply	other threads:[~2006-04-02 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-02 15:37 Gaëtan LEURENT [this message]
2006-04-03  1:37 ` Raid 4/5 small writes Neil Brown
     [not found]   ` <444282BB.6080407@tmr.com>
2006-04-16 22:37     ` Neil Brown

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=qlk3bgwt2dp.fsf@clipper.ens.fr \
    --to=gaetan.leurent@ens.fr \
    --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 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).