From: Christoph Hellwig <hch@infradead.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Heinz Mauelshagen <heinzm@redhat.com>,
linux-raid <linux-raid@vger.kernel.org>,
NeilBrown <neilb@suse.de>
Subject: Re: [dm-devel] [PATCH v2 1/1] dm-raid45
Date: Wed, 9 Dec 2009 05:43:09 -0500 [thread overview]
Message-ID: <20091209104309.GA8262@infradead.org> (raw)
In-Reply-To: <e9c3a7c20912081638w39469743n76b4114b840f1c43@mail.gmail.com>
On Tue, Dec 08, 2009 at 05:38:06PM -0700, Dan Williams wrote:
> Where did the investigation of reusing md/raid5.c [1] end up? This
> would simultaneously enable hardware accelerated raid6 for dmraid.
Yes, adding different raid code to dm is a bad idea, even more so after
Neil showed a useful prototype of reusing the md code.
next prev parent reply other threads:[~2009-12-09 10:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1259243112-28175-1-git-send-email-heinzm@redhat.com>
2009-12-09 0:38 ` [dm-devel] [PATCH v2 1/1] dm-raid45 Dan Williams
2009-12-09 10:43 ` Christoph Hellwig [this message]
2009-12-09 17:43 ` Heinz Mauelshagen
2009-12-09 17:47 ` Heinz Mauelshagen
2009-12-21 16:48 ` [dm-devel] " Dan Williams
2010-01-12 14:44 ` Heinz Mauelshagen
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=20091209104309.GA8262@infradead.org \
--to=hch@infradead.org \
--cc=dan.j.williams@intel.com \
--cc=dm-devel@redhat.com \
--cc=heinzm@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).