linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: SandeepKsinha <sandeepksinha@gmail.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID4 and RAID5 Code
Date: Fri, 15 May 2009 09:19:54 -0700	[thread overview]
Message-ID: <4A0D962A.5030309@zytor.com> (raw)
In-Reply-To: <37d33d830905150914v5d780e44s6cc2174944530ddb@mail.gmail.com>

SandeepKsinha wrote:
>>>
>> RAID 4 is really nothing but a block layout algorithm for RAID 5 (which
>> has four more block layout algorithms.)  RAID 6 contains all five under
>> one "level".
>>
> RAID 4 vs RAID 5
> Actually debatable. They have their own pros and cons and especially
> where you don't consider the physical properties of disk.
> Addition of new disk, differences in speed of disks, etc.. create
> bottlenecks especially in case of RAID5.
> 
> Except hot spot issue with RAID 4, I find it better than all others.
> Also, most of the proprietary solutions from IBM, Adaptec and NetApp
> suggest RAID4 as compared to others.
> 
> No offenses please, this is just an opinion.
> 

I was talking referring to how the implementation works.  However, it is
still nothing but a layout policy for the same data, even though it may
have quite different performance attributes.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2009-05-15 16:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-14 16:57 RAID4 and RAID5 Code SandeepKsinha
2009-05-15  1:23 ` Neil Brown
2009-05-15 16:08 ` H. Peter Anvin
2009-05-15 16:14   ` SandeepKsinha
2009-05-15 16:19     ` H. Peter Anvin [this message]
     [not found]     ` <4A0DB688.7050301@harddata.com>
2009-05-16  4:32       ` SandeepKsinha

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=4A0D962A.5030309@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=sandeepksinha@gmail.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).