linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: MRK <mrk@shiftmail.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Michael Evans <mjevans1983@gmail.com>,
	Bill Davidsen <davidsen@tmr.com>,
	Kaushal Shriyan <kaushalshriyan@gmail.com>,
	linux-raid@vger.kernel.org
Subject: Re: RAID5
Date: Fri, 23 Apr 2010 16:57:35 +0200	[thread overview]
Message-ID: <4BD1B55F.30702@shiftmail.org> (raw)
In-Reply-To: <4BD1AE0C.2040003@msgid.tls.msk.ru>

On 04/23/2010 04:26 PM, Michael Tokarev wrote:
>
> This is most likely due to read-modify-write cycle which is present on
> lvm-on-raid[456] if the number of data drives is not a power of two.
> LVM requires the block size to be a power of two, so if you can't fit
> some number of LVM blocks on whole raid stripe size your write speed
> is expected to be ~3 times worse...
>
> Even creating partitions on such raid array is difficult.
>
>
>
>    

Seriously?
a number of data drives power of 2 would be an immense limitation.
Why should that be? I understand that LVM blocks would not be aligned to 
raid stripes, and this can worsen the problem for random writes, but if 
the write is sequential, the raid stripe will still be filled at the 
next block-output by LVM.
Maybe the very first stripe you write will get an RMW but the next ones 
will be filled in the wait, and also consider you have the 
preread_bypass_threshold feature by MD which helps in this.

Also if you really need to put an integer number of LVM blocks in an MD 
stripe (which I doubt, as I wrote above), this still does not mean that 
the number of drives needs to be a power of 2: e.g. you could put 10 LVM 
blocks in 5 data disks, couldn't you?


I would think more to a barriers thing... I'd try to repeat the test 
with nobarrier upon ext4 mount and see.
But Bill says that he "knows" what's the problem so maybe he will tell 
us earlier or later :-)

  reply	other threads:[~2010-04-23 14:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19  3:46 RAID5 Kaushal Shriyan
2010-04-19  4:21 ` RAID5 Michael Evans
2010-04-21 13:32   ` RAID5 Bill Davidsen
2010-04-21 19:43     ` RAID5 Michael Evans
2010-04-23 14:26       ` RAID5 Michael Tokarev
2010-04-23 14:57         ` MRK [this message]
2010-04-23 20:57         ` RAID5 Michael Evans
2010-04-24  1:47           ` RAID5 Mikael Abrahamsson
2010-04-24  3:34             ` RAID5 Michael Evans
2010-05-02 22:51         ` RAID5 Bill Davidsen
2010-05-03  5:51         ` RAID5 Luca Berra
2010-05-02 22:45       ` RAID5 Bill Davidsen

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=4BD1B55F.30702@shiftmail.org \
    --to=mrk@shiftmail.org \
    --cc=davidsen@tmr.com \
    --cc=kaushalshriyan@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mjevans1983@gmail.com \
    --cc=mjt@tls.msk.ru \
    /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).