All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Flory <sflory@rackable.com>
To: "Måns Rullgård" <mru@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Software RAID5 with 2.6.0-test
Date: Fri, 17 Oct 2003 11:39:36 -0700	[thread overview]
Message-ID: <3F903768.7060803@rackable.com> (raw)
In-Reply-To: <yw1xu167kbcw.fsf@users.sourceforge.net>

Måns Rullgård wrote:
> Bill Davidsen <davidsen@tmr.com> writes:
> 
> 
>>>However, I wouln't count on superior performance from software based
>>>RAID 5 (ata/fakeraid or otherwise), that is whats real raid controllers
>>>are for.
>>
>>While an overloaded system may benefit from offloaded the CPU
>>requirements of RAID, unless you go to a very expensive external unit
>>the kernel RAID will usually outperform the inexpensive RAID embedded on
>>a controller. The kernel simply knows more about the data needs and can
>>can do things a controller can't.
> 
> 
> What about the RAID controllers in the $400 category?  Surely, they
> must be doing something better than the $50 fakeraid controllers.
> 

   Yes, but follow this logic.

1)You are willing to devote 10% of 2Ghz xeon to software raid.
2)A $500+ controller has a 100Mhz proccessor.

   Thus just from this you could guess that software raid has x2 as many 
clock cycles availble to it.  It's even worse when you realize the 2Ghz 
xeon is a better proccessor in many more ways than just clock cycles.


   The reasons to use that 500-1000 raid controller are due the features 
the controller gives you.  Things like gracefull recovery from bad 
sectors, and SAF-TE support.


-- 
Once you have their hardware. Never give it back.
(The First Rule of Hardware Acquisition)
Sam Flory  <sflory@rackable.com>


  reply	other threads:[~2003-10-17 18:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-08 22:43 Software RAID5 with 2.6.0-test Måns Rullgård
2003-10-08 23:24 ` Torrey Hoffman
2003-10-08 23:44   ` Måns Rullgård
2003-10-09  0:51     ` Andre Tomt
2003-10-09  8:55       ` Måns Rullgård
2003-10-09  9:10         ` Andre Tomt
2003-10-09  9:28           ` Måns Rullgård
2003-10-17 17:07           ` Bill Davidsen
2003-10-17 17:44             ` Måns Rullgård
2003-10-17 18:39               ` Samuel Flory [this message]
2003-10-17 19:18                 ` Måns Rullgård
2003-10-17 19:37                   ` Jakob Oestergaard
2003-10-17 19:52                     ` Måns Rullgård
2003-10-18 22:55                   ` jw schultz
2003-10-17 19:24               ` Jakob Oestergaard
2003-10-19  9:25                 ` Pavel Machek
2003-10-21 21:44                 ` bill davidsen
2003-10-21 21:36               ` bill davidsen
2003-10-22 15:17                 ` Chuck Campbell
2003-10-18 11:50 Dr. David Alan Gilbert
2003-10-21 21:51 ` bill davidsen
2003-10-22  2:37   ` jw schultz

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=3F903768.7060803@rackable.com \
    --to=sflory@rackable.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mru@users.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.