From: Thomas Horsten <thomas@horsten.com>
To: Lars Marowsky-Bree <lmb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: Driver for BIOS-based software RAIDs
Date: Mon, 13 Oct 2003 22:38:40 +0100 [thread overview]
Message-ID: <200310132238.40012.thomas@horsten.com> (raw)
In-Reply-To: <20031013211722.GG23916@marowsky-bree.de>
On Monday 13 October 2003 22:17, Lars Marowsky-Bree wrote:
> "BIOS RAIDs" is a rather sweet euphemism for "crippled pretense of
> hardware RAID, which is in fact emulated by software". I've got no
> problem with telling the users that what they have _is_ software RAID
> and needs to be treated as such.
I completely agree with you, and I will make sure my drivers print "Software
RAID" all over the screen when it loads :-) Ok, at least on one line then.
I'm not on a mission to justify the marketing methods of chip manufactureres.
Having said that, BIOS RAID does solve a few problems inherent to software
RAID's, particularly the boot process and consistency of RAID's between
operating systems. I want to leverage those advantages and I think that this
is best done with an autodetecting driver.
> Windows doesn't use the BIOS to access the device at all; the
> corresponding hardware drivers emulate that.
I know, but the BIOS supports its boot up to 32-bit mode. Which means you
could see the drive from DOS, etc. And putting the RAID in BIOS does have
some advantages for the average PC motherboard.
Best regards,
Thomas
next prev parent reply other threads:[~2003-10-13 21:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 18:21 Driver for BIOS-based software RAIDs Thomas Horsten
2003-10-13 18:31 ` Kevin P. Fleming
2003-10-13 19:19 ` Thomas Horsten
2003-10-13 19:03 ` Lars Marowsky-Bree
2003-10-13 19:25 ` Thomas Horsten
2003-10-13 21:17 ` Lars Marowsky-Bree
2003-10-13 21:38 ` Thomas Horsten [this message]
2003-10-14 7:18 ` Lars Marowsky-Bree
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=200310132238.40012.thomas@horsten.com \
--to=thomas@horsten.com \
--cc=linux-raid@vger.kernel.org \
--cc=lmb@suse.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 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.