From: Jeff Garzik <jgarzik@pobox.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Bernd Eckenfels <ecki-news2004-05@lina.inka.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux SATA RAID FAQ
Date: Thu, 12 Aug 2004 13:23:45 -0400 [thread overview]
Message-ID: <411BA7A1.403@pobox.com> (raw)
In-Reply-To: <1092315392.21994.52.camel@localhost.localdomain>
Alan Cox wrote:
> end devices (eg aacraid sata boards). There are also some low end
> devices with part of the raid logic in hardware (some promise) although
> I don't believe we use that to the full yet.
Nope. My SATA RAID FAQ mentions the Promise "RAID accelerator" stuff.
In particular, the Promise SX4 is in fact likely to be faster with the
_Promise_ RAID driver, rather than the Linux non-RAID driver.
I really like the SX4, and wish Linux could make better use of it...
The SX4 has an on-board DIMM (128M - 2G), through which all data _must_
pass. The data transfer between host and on-board DIMM is a separate
DMA engine and separate interrupt event from the four ATA DMA engines
(one per SATA port). There are several possibilities that are worth
exploring on this card:
* Caching
* Eliminate PCI bus traffic by sending RAID1/5 writes a _single_ time to
the card, and then multiplex to multiple attached drives from there
* Offload RAID5 XOR calculations, which becomes quite useful in
combination with these other features
* Execute RAID1/5 resyncs and parity checks completely on the card
I have full docs and knowledge, but no idea how to hook this stuff into
Linux md efficiently.
Jeff
next prev parent reply other threads:[~2004-08-12 17:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 6:33 Linux SATA RAID FAQ Jeff Garzik
2004-08-12 7:18 ` Michael Knigge
2004-08-12 11:17 ` Paul Ionescu
2004-08-12 11:34 ` Willy Tarreau
2004-08-12 13:38 ` Bernd Eckenfels
2004-08-12 12:56 ` Alan Cox
2004-08-12 17:23 ` Jeff Garzik [this message]
2004-08-12 17:30 ` Jeff Garzik
2004-08-14 21:49 ` Alan Cox
2004-08-14 22:56 ` Jeff Garzik
2004-08-15 20:54 ` Xavier Bestel
2004-08-15 20:51 ` Alan Cox
2004-08-15 22:02 ` Bernd Eckenfels
2004-08-15 21:42 ` Jakob Oestergaard
2004-08-16 22:06 ` Andrew Morton
2004-08-16 21:58 ` Alan Cox
2004-08-16 22:10 ` Christoph Hellwig
2004-08-12 14:01 ` Alistair John Strachan
2004-08-14 0:31 ` J. Ryan Earl
2004-08-14 3:17 ` Mark Lord
2004-08-14 6:37 ` age huisman
2004-08-14 11:03 ` Mark Lord
2004-08-14 15:21 ` Alan Cox
2004-08-14 22:28 ` J. Ryan Earl
2004-08-12 18:09 ` Martin Schlemmer
-- strict thread matches above, loose matches on Subject: below --
2004-08-12 13:46 Dieter Stueken
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=411BA7A1.403@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ecki-news2004-05@lina.inka.de \
--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