mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jw schultz <jw@pegasys.ws>
To: linux-kernel@vger.kernel.org
Subject: Re: Software RAID5 with 2.6.0-test
Date: Sat, 18 Oct 2003 15:55:21 -0700	[thread overview]
Message-ID: <20031018225521.GA3699@pegasys.ws> (raw)
In-Reply-To: <yw1xllrjk70f.fsf@users.sourceforge.net>

On Fri, Oct 17, 2003 at 09:18:24PM +0200, Måns Rullgård wrote:
> Samuel Flory <sflory@rackable.com> writes:
> 
> >> 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.
> 
> How about this logic:
> 
> 1) If the processor on the RAID controller can handle the full
> bandwidth of the disks, it's fast enough.
> 2) If someone else does the 10% work, the CPU can do 10% more work.

And as has been addressed on this list before:

3) If the additional I/O traffic of the RAID can be kept off
of the system busses the overall system throughput goes up.

Once the CPU reaches a certain level of performance it is
the I/O and memory that limit things.  Do you really want to
pollute L1 cache with RAID-5?  When the $400 RAID server
card can saturate the PCI buss it doesn't matter how much
spare CPU you have, SW RAID will not be able to match the
performance.


-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws

		Remember Cernan and Schmitt

  parent reply	other threads:[~2003-10-18 22:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-08 22:43 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
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 [this message]
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=20031018225521.GA3699@pegasys.ws \
    --to=jw@pegasys.ws \
    --cc=linux-kernel@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

Powered by JetHome