linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Drew <drew.kay@gmail.com>
Cc: Zdenek Kaspar <zkaspar82@gmail.com>,
	linux-raid@vger.kernel.org, dm-devel@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: Linux RAID subsystem future
Date: Fri, 13 Jul 2012 06:35:01 +1000	[thread overview]
Message-ID: <20120713063501.3f9a3bd8@notabene.brown> (raw)
In-Reply-To: <CACJz6Qsx-xNxDRw5kUqUpf9ogVp23jokHOdGL9xO=kqFXmiNZg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

On Thu, 12 Jul 2012 13:28:24 -0700 Drew <drew.kay@gmail.com> wrote:

> > Hello lists,
> >
> > I noticed recent patches added MD RAID compatibility into the DM
> > subsystem. Is there a valid reason to duplicate efforts ?
> >
> > Hopefully its not silent preparation step for DM takeover. Can someone
> > shed more light on this topic ?
> >
> > TIA, Z.
> 
> I'm not a developer by any stretch of the word so take what I say with
> a grain of salt.
> 
> I think it's more just a case of dm using md's RAID algorithms, which
> IMHO are better tested, to support fakeraid controllers like Intel's
> Matrix RAID. Besides, we're all one big happy linux family so why not
> borrow your brother's socks? :-)
> 
> 
Indeed!

It isn't duplication of effort - it is avoiding or removing duplication of
effort.  That's the theory any way.

There is no "DM takeover" - just engineers working together to try to find
optimal solutions.

NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-07-12 20:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12 17:26 Linux RAID subsystem future Zdenek Kaspar
2012-07-12 20:28 ` Drew
2012-07-12 20:35   ` NeilBrown [this message]
2012-07-14 21:41     ` Zdenek Kaspar

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=20120713063501.3f9a3bd8@notabene.brown \
    --to=neilb@suse.de \
    --cc=dm-devel@redhat.com \
    --cc=drew.kay@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=zkaspar82@gmail.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;
as well as URLs for NNTP newsgroup(s).