public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joel Jaeggli <joelja@uoregon.edu>
To: Marc Perkel <marc@perkel.com>
Cc: Tejun Heo <htejun@gmail.com>, Andre Tomt <andre@tomt.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Hardware vs. Software Raid Speed
Date: Wed, 23 Aug 2006 22:13:49 -0700	[thread overview]
Message-ID: <44ED358D.30602@uoregon.edu> (raw)
In-Reply-To: <44EC9699.3040001@perkel.com>



Marc Perkel wrote:
> 
> 
> Tejun Heo wrote:
>> Andre Tomt wrote:
>>> Marc Perkel wrote:
>>>> Running Linux on an AMD AM2 nVidia chip ser that supports Raid 0
>>>> striping on the motherboard. Just wondering if hardware raid (SATA2) 
>>
>> SATA2 has nothing to do with hardware RAID.
>>
>>>> is going to be faster that software raid and why?
>>>
>>> Beeing a consumer type board (AM2), the "raid on the motherboard" is
>>> in 99.999% of the cases just software raid implemented in their
>>> Windows drivers, a bootup setup screen plus some BIOS magic to get
>>> the OS booting.
>>
>> And, yeah, they're all software RAID.  Also, there isn't much to be
>> gained from making RAID0/1 hardware.  The software overhead isn't that
>> big.  For RAID5, having XOR done in hardware helps.
>>
> 
> Thanks - I suspected that Raid 0 didn't gain anything in hardware unless
> they provided additional buffering or something but I just thought I'd
> ask in case there was something I was overlooking.

A hardware raid controller can buy you a battery backed write cache, so
there are potentially some performance/safety benefits potentially.

We have a mix of software raid and 3ware based hardware raid subsystems.
For the applications we support, in general I can say that performance
was not the discriminating reason to choose one over the other.

> -
> 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/

-- 
------------------------------------------------------------------------
Joel Jaeggli             Unix Consulting              joelja@uoregon.edu
GPG Key Fingerprint:   5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2

  reply	other threads:[~2006-08-24  5:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23  6:52 Hardware vs. Software Raid Speed Marc Perkel
2006-08-23  7:25 ` Andre Tomt
2006-08-23  8:39   ` Alistair John Strachan
2006-08-23 17:47   ` Tejun Heo
2006-08-23 17:55     ` Marc Perkel
2006-08-24  5:13       ` Joel Jaeggli [this message]
2006-08-23 19:42     ` Mario 'BitKoenig' Holbe

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=44ED358D.30602@uoregon.edu \
    --to=joelja@uoregon.edu \
    --cc=andre@tomt.net \
    --cc=htejun@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc@perkel.com \
    /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