From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-raid@vger.kernel.org
Subject: Re: dmraid - where is the raid done?
Date: Tue, 28 Oct 2008 07:49:07 -0400 [thread overview]
Message-ID: <1225194547.16984.69.camel@pc.ilinx> (raw)
In-Reply-To: <490666F0.4000306@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
On Mon, 2008-10-27 at 20:12 -0500, Roger Heflin wrote:
>
> If it is an out-of-kernel driver, then the work is being done in the
> manufacturer's driver.
I see.
> If it is dmraid it is being done in the dmraid driver.
Ahhh. So in the above "out of kernel driver" instance that is a case
where dmraid is not handling it, yes?
> If there is no underlying hardware to run the raid on then everything has
> to be done in the OS.
Indeed. I had just wondered if these "fakeraid" solutions where at
least fanning out the copy (in the case of mirror) themselves, saving
the doubling of PCI bus traffic.
> All of the real raid cards have at least a
> really basic microprocesser on the card that takes care of things.
Yeah, I'm fairly familiar with the concepts of real RAID hardware. It
was this new fakeraid I was wondering about.
Thanx for the enlightenment though. The one last value that I had hope
for in the fakeraid arena seems to be invalid so I have to start to
agree with the documentation I've read and really have to wonder the
value of the fakeraid, especially and until the on-disk formats are
standardized. Not being able to move fakeraid disks from one
manufacturer to another is a real impediment in my mind.
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-28 11:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 15:07 dmraid - where is the raid done? Brian J. Murrell
2008-10-27 23:29 ` Roger Heflin
2008-10-28 0:36 ` Brian J. Murrell
2008-10-28 1:12 ` Roger Heflin
2008-10-28 11:49 ` Brian J. Murrell [this message]
2008-10-28 12:10 ` Mario 'BitKoenig' Holbe
2008-10-27 23:38 ` Mario 'BitKoenig' Holbe
2008-10-28 0:32 ` Dan Williams
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=1225194547.16984.69.camel@pc.ilinx \
--to=brian@interlinx.bc.ca \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).