From: "Chris Friesen" <cfriesen@nortel.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linux RAID Mailing List <linux-raid@vger.kernel.org>,
marc@perkel.com
Subject: Re: Linux: Why software RAID?
Date: Wed, 23 Aug 2006 23:20:35 -0600 [thread overview]
Message-ID: <44ED3723.3090308@nortel.com> (raw)
In-Reply-To: <44ED1E41.40606@garzik.org>
Jeff Garzik wrote:
> But anyway, to help answer the question of hardware vs. software RAID, I
> wrote up a page:
>
> http://linux.yyz.us/why-software-raid.html
Just curious...with these guys
(http://www.bigfootnetworks.com/KillerOverview.aspx) putting linux on a
PCI NIC to allow them to bypass Windows' network stack, has anyone ever
considered doing "hardware" raid by using an embedded cpu running linux
software RAID, with battery-backed memory?
It would theoretically allow you to remain feature-compatible by
downloading new kernels to your RAID card.
Chris
next prev parent reply other threads:[~2006-08-24 5:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 3:34 Linux: Why software RAID? Jeff Garzik
2006-08-24 4:22 ` Richard Scobie
2006-08-24 8:19 ` Jeff Garzik
2006-08-24 20:08 ` Richard Scobie
2006-08-24 5:20 ` Chris Friesen [this message]
2006-08-24 5:25 ` H. Peter Anvin
2006-08-26 20:55 ` Dan Williams
2006-08-24 5:43 ` Mattias Wadenstein
2006-08-24 13:07 ` Adam Kropelin
2006-08-24 13:20 ` Alan Cox
2006-08-24 13:36 ` Adam Kropelin
2006-08-24 13:42 ` Gordon Henderson
2006-09-04 17:29 ` Bill Davidsen
2006-08-24 14:55 ` Mark Lord
[not found] ` <44EDB843.2020608@perkel.com>
2006-08-24 15:21 ` Alan Cox
2006-09-04 17:31 ` Bill Davidsen
2006-09-04 17:31 ` Joel Jaeggli
-- strict thread matches above, loose matches on Subject: below --
2006-08-26 3:50 linux
2006-08-26 12:18 ` Raz Ben-Jehuda(caro)
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=44ED3723.3090308@nortel.com \
--to=cfriesen@nortel.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@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 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.