From: Luigi Genoni <kernel@Expansa.sns.it>
To: Thunder from the hill <thunder@ngforever.de>
Cc: linux-kernel@vger.kernel.org, Martin Eriksson <nitrax@giron.wox.org>
Subject: Re: HPT370 RAID-1 or Software RAID-1, what's "best"?
Date: Fri, 15 Mar 2002 17:52:47 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0203151716120.30388-100000@Expansa.sns.it> (raw)
In-Reply-To: <3C920ABB.6E17E324@ngforever.de>
On Fri, 15 Mar 2002, Thunder from the hill wrote:
> Hi,
>
> Luigi Genoni wrote:
> > HPT370 IDE Raid is not really an hardware raid.
> > It is a software Raid, since Linux does not use tha raid implementation
> > that comes with the BIOS, but it uses softwareraid.
> That doesn't prevent me from saying that real hardware raid might be
> better. But is the thing you wish to say that there's no difference, or
> what?
Hardware RAID is indeed better, but what you get using HPT370 IDE
controlelr is not hardware raid at all. Just read the code of the driver.
You get a software raid, period.
>
> Alan Cox wrote:
> > The raid rebuild time is identical for pretty much any set up. With the
> > softraid its intentionally defaulting to a low fraction of I/O bandwidth
> > so it doesnt disrupt normal operation.
> I experienced it took at about twice the time for a rebuild. I don't
> exactly remember the test results, and they aren't available to me until
> Monday. If you're interested...
> Maybe things have changed a lot since last year, when I did the tests.
>
> > Also as far is his question goes - both are software raid
> See above.
>
> Thunder
> --
> begin-base64 755 -
> IyEgL3Vzci9iaW4vcGVybApteSAgICAgJHNheWluZyA9CSMgVGhlIHNjcmlw
> dCBvbiB0aGUgbGVmdCBpcyB0aGUgcHJvb2YKIk5lbmEgaXN0IGVpbiIgLgkj
> IHRoYXQgaXQgaXNuJ3QgYWxsIHRoZSB3YXkgaXQgc2VlbXMKIiB2ZXJhbHRl
> dGVyICIgLgkjIHRvIGJlIChlc3BlY2lhbGx5IG5vdCB3aXRoIG1lKQoiTkRX
> LVN0YXIuXG4iICA7CiRzYXlpbmcgPX4Kcy9ORFctU3Rhci9rYW5uXAogdW5z
> IHJldHRlbi9nICA7CiRzYXlpbmcgICAgICAgPX4Kcy92ZXJhbHRldGVyL2Rp
> XAplIExpZWJlL2c7CiRzYXlpbmcgPX5zL2Vpbi8KbnVyL2c7JHNheWluZyA9
> fgpzL2lzdC9zYWd0LC9nICA7CiRzYXlpbmc9fnMvXG4vL2cKO3ByaW50Zigk
> c2F5aW5nKQo7cHJpbnRmKCJcbiIpOwo=
> ====
> Extract this and see what will happen if you execute my
> signature. Just save it to file and do a
> > uudecode $file | perl
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2002-03-15 16:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 14:52 HPT370 RAID-1 or Software RAID-1, what's "best"? Thunder from the hill
2002-03-15 15:29 ` Alan Cox
2002-03-15 16:52 ` Luigi Genoni [this message]
2002-03-15 17:43 ` Alan Cox
2002-03-15 18:07 ` Luigi Genoni
2002-03-16 1:12 ` Mike Fedyk
2002-03-18 19:56 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2002-03-14 18:33 Thunder from the hill
2002-03-14 18:53 ` Alan Cox
2002-03-15 9:31 ` Luigi Genoni
2002-03-15 12:59 ` Martin Eriksson
2002-03-15 14:00 ` Ulrich Wiederhold
2002-03-13 21:20 Martin Eriksson
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=Pine.LNX.4.44.0203151716120.30388-100000@Expansa.sns.it \
--to=kernel@expansa.sns.it \
--cc=linux-kernel@vger.kernel.org \
--cc=nitrax@giron.wox.org \
--cc=thunder@ngforever.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).