linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gregory Leblanc <gleblanc@linuxweasel.com>
To: linux-raid@vger.kernel.org
Subject: Re: EIO AP-1680 ATA133 RAID PCI Controller
Date: 11 Feb 2003 13:16:31 -0800	[thread overview]
Message-ID: <1044998190.12695.3.camel@gregdell> (raw)
In-Reply-To: <3E493005.4030702@mvista.com>

[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]

On Tue, 2003-02-11 at 09:16, Steven Dake wrote:
> I don't know the specifics of those cards, but if they include an i/o 
> processor, they are a hardware RAID.
> 
> Keep in mind that unless you want to boot or use a RAID 5, or want to 
> share your RAID volumes between different operating systems, there is 
> little reason to purchase a hardware RAID card.  Software RAID is quite 
> sufficient for most needs and the host processor running at 2+ ghz is 
> much better at RAID then a 60 mhz i960 IOP.  Keep in mind, though, that 
> hardware RAID adaptors have built in xor accelerators which can do 
> multiple xors in one instruction in hardware, allowing for much better 
> xor performance then the intel or ppc processor can do.

While the performance of RAID 5 using software RAID is generally far
superior to that provided by hardware RAID, host CPU usage can be
-quite- high in high-load situations.  The benchmarks recently posted
had cpu usage numbers at over 90% on most sequeential writes and reads.
	Greg

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-02-11 21:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-07  3:36 EIO AP-1680 ATA133 RAID PCI Controller tk Voice
2003-02-10 17:32 ` Steven Dake
2003-02-11  5:16   ` tk Voice
2003-02-11 17:16     ` Steven Dake
2003-02-11 21:16       ` Gregory Leblanc [this message]
2003-02-11 18:55         ` Trent Piepho
2003-02-12 15:36         ` Maurice Hilarius
2003-02-12 23:00           ` Gregory Leblanc

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=1044998190.12695.3.camel@gregdell \
    --to=gleblanc@linuxweasel.com \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).