From: Martin Dalecki <dalecki@evision-ventures.com>
To: "Jakob Østergaard" <jakob@unthought.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Pavel Machek <pavel@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: IDE hotplug support?
Date: Thu, 02 May 2002 22:18:33 +0200 [thread overview]
Message-ID: <3CD19F19.2030104@evision-ventures.com> (raw)
In-Reply-To: <20020502215833.V31556@unthought.net> <E173N9y-0004k1-00@the-village.bc.nu> <20020502231359.W31556@unthought.net>
Uz.ytkownik Jakob Østergaard napisa?:
> On Thu, May 02, 2002 at 09:26:38PM +0100, Alan Cox wrote:
>
>>>>=20
>>>>8 x 130MBy/s >>>> PCI bus throughput... I would rather recommend
>>>>a classical RAID controller card for this kind of
>>>>setup.
>>>
>>>Because RAID controllers do not use the PCI bus ??? ;)
>>
>>The raid card transfers the data once, software raid once per device for
>>Raid 1/5 - thats a killer.
>
>
> For RAID-1 it's a killer (for writes), I agree.
>
> But I really doubt it would be so horrible for RAID-5 - after all, it's only
> one extra block (the parity block) for each N-1 blocks written (for an N disk
> RAID-5). The penalty should be less, the more disks you have in the array.
>
> But seriously, has anyone out there ever seen a hardware RAID controller with
> a *sustained* RAID-5 thoughput of more than 60 MB/sec ? Not that I think it
> is impossible, but I've never heard about it. Enlighten me, please, and not
> with marketing numbers...
Go to Sun hardware and you will see it quite frequently even on a simple
E450 equipped with an external RAID box. I saw them frequently enough in
sar accounts when the system was configured to trash on a swap
partition, which resided on such a RAID.
64 bit buses win here by a huge margin.
next prev parent reply other threads:[~2002-05-02 21:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 15:48 IDE hotplug support? Roy Sigurd Karlsbakk
2002-04-26 15:29 ` Pavel Machek
2002-05-02 18:19 ` Martin Dalecki
2002-05-02 19:58 ` Jakob Østergaard
2002-05-02 20:09 ` Samuel Flory
2002-05-03 0:31 ` Roy Sigurd Karlsbakk
2002-05-03 3:14 ` jw schultz
2002-05-02 20:26 ` Alan Cox
2002-05-02 21:13 ` Jakob Østergaard
2002-05-02 20:18 ` Martin Dalecki [this message]
2002-05-02 22:22 ` Jeff Nguyen
2002-05-02 23:09 ` Jakob Østergaard
2002-05-03 0:16 ` Alan Cox
2002-05-03 0:35 ` Roy Sigurd Karlsbakk
2002-05-03 17:10 ` Roy Sigurd Karlsbakk
2002-05-03 0:25 ` Roy Sigurd Karlsbakk
2002-05-03 0:51 ` Alan Cox
2002-05-03 0:37 ` Roy Sigurd Karlsbakk
2002-04-30 16:22 ` Zwane Mwaikambo
2002-04-30 18:46 ` Ragnar Hojland Espinosa
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=3CD19F19.2030104@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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.