From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: Best Low-cost IDE RAID Solution For 2.6.x? (OT?)
Date: 7 Jan 2004 23:28:44 GMT [thread overview]
Message-ID: <bti4nc$7qj$1@gatekeeper.tmr.com> (raw)
In-Reply-To: Pine.LNX.4.44.0312281516060.21070-100000@twin.uoregon.edu
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2900 bytes --]
In article <Pine.LNX.4.44.0312281516060.21070-100000@twin.uoregon.edu>,
Joel Jaeggli <joelja@darkwing.uoregon.edu> wrote:
| on the low-end promise controllers (ie everything but the sx4000 and
| sx6000) it's not hardware raid, it's the driver doing raid in this case
| the promise fastrack driver. among other things their driver doesn't do
| raid 5, just 0 1 or 0+1. so software raid does raid 5 and more.
|
| to quote the config_blk_dev_ataraid:
|
| CONFIG_BLK_DEV_ATARAID:
| âSay Y or M if you have an IDE Raid controller and want linux
| âto use its softwareraid feature. You must also select an
| appropriate for your board low-level driver below.
|
| âNote, that Linux does not use the Raid implementation in BIOS, and
| âthe main purpose for this feature is to retain compatibility and
| âdata integrity with other OS-es, using the same disk array. Linux
| âhas its own Raid drivers, which you should use if you need better
| âperformance.
|
| I've also had two if the higher-end promise sx6000's and the suffering I
| incurred making them work with the i2o drivers particularly when promise
| revised the bioses on those cards means I can't recomend them for much.
|
| > raid instead, what would be the CPU overhead?
|
| The linux software raid layer is actually faster under most circumstances
| the hardware raid controllers, doing raid5. but since the promise can't
| actually do that (raid 5) anyway it's hard to compare them directly. the
| 3ware cards in my experience result in lower cpu utilization for i/o but
| there hardware tops out at 80-145MB/s depending on model and we have
| software raid subsystems that go faster than that at the expense of some
| of the rather bountiful cpu we have in those boxes.
The problem with the Linux software RAID is that's in the kernel. So if
the boot disk dies you don't get to boot and use the kernel. With the
controller RAID you do use the the RAID-1 copy, and boot, and sometimes
that's the feature which counts more than all the rest.
Now if you run LinuxBIOS you CAN do this all yourself, but unless you do
there are still some reliability issues.
Also note that if you do mirroring you use twice as much disk buffer
space to queue two writes, which could impact the performance in a low
memory system. That's theory, I haven't benchmarked.
Promise used to make a little adaptor which did RAID-1 on two drives and
made them look like one. This was not at the controller as I recall, but
in the cable, where the data was split. That would give boot reliability
without losing a device pair, but I have no idea how well it worked
other than in a demonstration.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2004-01-07 23:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-28 18:04 Best Low-cost IDE RAID Solution For 2.6.x? (OT?) Johannes Ruscheinski
2003-12-28 18:50 ` Joel Jaeggli
2003-12-28 21:35 ` Johannes Ruscheinski
2003-12-28 21:45 ` Arjan van de Ven
2003-12-28 22:14 ` Johannes Ruscheinski
2003-12-28 23:05 ` H. Peter Anvin
2003-12-29 1:18 ` Wakko Warner
2003-12-28 21:56 ` bert hubert
2003-12-28 23:36 ` Joel Jaeggli
2004-01-07 23:28 ` bill davidsen [this message]
2003-12-29 2:10 ` Samuel Flory
2003-12-29 13:41 ` Tomas Szepe
2003-12-29 18:59 ` Johannes Ruscheinski
2003-12-29 19:04 ` Samuel Flory
2003-12-29 19:06 ` Tomas Szepe
2003-12-30 0:03 ` Wakko Warner
2003-12-30 6:54 ` Tomas Szepe
2003-12-30 14:41 ` Wakko Warner
2003-12-30 20:58 ` Samuel Flory
2004-01-07 23:35 ` bill davidsen
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='bti4nc$7qj$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--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