linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Neil Brown <neilb@suse.de>,
	linux-raid@vger.kernel.org,
	pkg-mdadm-devel@lists.alioth.debian.org
Subject: Re: write-intent bitmaps
Date: Tue, 29 Jan 2008 18:32:14 +1100	[thread overview]
Message-ID: <200801291832.18375.russell@coker.com.au> (raw)
In-Reply-To: <479E1BB3.2080702@tmr.com>

On Tuesday 29 January 2008 05:15, Bill Davidsen <davidsen@tmr.com> wrote:
> You may have missed the "much higher" part of the previous paragraph.
> And given the reliability of modern drives, unless you have a LOT of
> them you may be looking at years of degraded performance to save a few
> hours of slow performance after a power fail or similar. In other words,
> it's not as black and white as it seems.

What is the pathological case?  1/2 or 1/3 write performance?

For serious write performance of a RAID you want a NVRAM write-back cache for 
RAID-5 stripes, and the NVRAM cache removes the need for write-intent 
bitmaps.  AFAIK Linux software RAID doesn't support such things and that 
putting filesystem journals and the write-intent bitmap blocks on NVRAM 
devices is the best that you could achieve.

It seems that if you want the best performance for small synchronous writes 
(EG a mail server - which may be the most pessimal application for 
write-intent bitmaps) then hardware RAID is the only option.

Are there plans for supporting a NVRAM write-back cache with Linux software 
RAID?

-- 
russell@coker.com.au
http://etbe.coker.com.au/          My Blog

http://www.coker.com.au/sponsorship.html Sponsoring Free Software development

  parent reply	other threads:[~2008-01-29  7:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-27 10:34 write-intent bitmaps Russell Coker
2008-01-27 11:21 ` Neil Brown
2008-01-27 15:12   ` Russell Coker
     [not found]     ` <479E1BB3.2080702@tmr.com>
2008-01-29  7:32       ` Russell Coker [this message]
2008-01-29  9:13         ` Peter Rabbitson
2008-01-29  9:40           ` Russell Coker

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=200801291832.18375.russell@coker.com.au \
    --to=russell@coker.com.au \
    --cc=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=pkg-mdadm-devel@lists.alioth.debian.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).