linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "Ralph Paßgang" <ralph@debianbase.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Which raid card to buy for Sarge
Date: Wed, 31 Mar 2004 15:59:26 -0500	[thread overview]
Message-ID: <406B312E.1030006@pobox.com> (raw)
In-Reply-To: <200403312242.49462.ralph@debianbase.de>

Ralph Paßgang wrote:
> kernel code). But normaly a real hardware raid is without a doubt faster than 
> a software raid.


Well...  Regardless of hardware or software RAID, the kernel I/O limits 
and the drive I/O limits are the main limiting factor.  Hardware RAID 
mainly helps for RAID1 and RAID5 writes, eliminating duplicate copies of 
data going across the PCI bus... at the expense of relinquishing control 
over your data to the hardware RAID's firmware.

A UDMA/133 PATA hardware RAID from a large company I won't mention is 
quite a bit slower than any SATA software RAID that I've tested...

	Jeff



-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2004-03-31 20:59 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-31 15:47 Which raid card to buy for Sarge me
2004-03-31 16:15 ` Luca Berra
2004-03-31 16:43   ` me
2004-03-31 16:58     ` Måns Rullgård
2004-03-31 18:03       ` Ralph Paßgang
2004-03-31 19:50         ` Mark Hahn
2004-03-31 20:19           ` Richard Scobie
2004-04-01  9:07             ` KELEMEN Peter
2004-04-04  4:47               ` Richard Scobie
2004-04-09 11:16                 ` KELEMEN Peter
2004-04-09 13:07                   ` Which raid card to buy for SargeD Yu Chen
2004-04-09 21:52                     ` KELEMEN Peter
2004-03-31 20:42           ` Which raid card to buy for Sarge Ralph Paßgang
2004-03-31 20:59             ` Jeff Garzik [this message]
2004-03-31 21:39             ` Guy
2004-04-01  4:49           ` Brad Campbell
2004-04-01  4:51             ` seth vidal
2004-04-01  5:01               ` Brad Campbell
2004-04-01  5:39                 ` Guy
2004-04-01  5:51                   ` Brad Campbell
2004-04-01  5:29             ` Guy
2004-04-01  5:54               ` Jeff Garzik
2004-04-01  5:44             ` Jeff Garzik
2004-04-01  5:56               ` Brad Campbell
2004-04-01  7:49                 ` Sandro Dentella
2004-04-01  8:03                   ` Brad Campbell
2004-04-01  8:07                   ` Jeff Garzik
2004-04-16 14:25             ` Nick Maynard
2004-04-16 15:09               ` Måns Rullgård
2004-04-16 16:29                 ` Nick Maynard
2004-04-16 17:44                   ` Måns Rullgård
2004-04-16 22:34                   ` jlewis
2004-04-01  4:24 ` me
2004-04-01  4:57   ` Clemens Schwaighofer
2004-04-01  5:34     ` Jeff Garzik
2004-04-01  6:39       ` Clemens Schwaighofer
2004-04-01  5:58   ` Jeff Garzik
2004-04-01 12:52     ` me
2004-04-01 19:31       ` Terrence Martin
2004-04-02  4:46         ` me

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=406B312E.1030006@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=ralph@debianbase.de \
    /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).