From: Kevin Corry <corryk@us.ibm.com>
To: Lars Marowsky-Bree <lmb@suse.de>, evms-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: EVMS announcement
Date: Wed, 6 Nov 2002 09:08:43 -0600 [thread overview]
Message-ID: <02110609084300.06245@boiler> (raw)
In-Reply-To: <20021106001607.GJ27832@marowsky-bree.de>
On Tuesday 05 November 2002 18:16, Lars Marowsky-Bree wrote:
> Now, an interesting question is whether the md modules etc will simply be
> continued to be used or whether they'll make use of the DM engine too? Can
> they be made "plugins" to DM or the EVMS framework?
I think the MD kernel modules certainly *could* be ported to the dev-mapper
framework. But right now, from EVMS's standpoint, there is no need to force
that change just yet. If it is determined in the future that that would be a
better direction to go, for us it would just mean re-coding the user-space MD
plugin to talk to dev-mapper instead of the MD driver. But a lot of work has
gone into the MD driver during 2.5, so I would personally think such a change
won't happen until at least 2.7.
> Or even, could EVMS (in
> theory) parse the meta-data from a legacy md device and just setup a DM
> mapping for it? That would appeal to me quite a bit. I really need to start
> reading up on it...
The pretty much exactly what does/will happen, except EVMS will talk to the
MD driver now (maybe DM in the future).
--
Kevin Corry
corryk@us.ibm.com
http://evms.sourceforge.net/
next prev parent reply other threads:[~2002-11-06 15:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 22:19 EVMS announcement Kevin Corry
2002-11-05 21:00 ` [Evms-announce] " Mike Diehl
2002-11-05 21:11 ` Mike Diehl
2002-11-05 23:53 ` Rik van Riel
2002-11-06 0:21 ` Alan Cox
2002-11-06 9:34 ` [Evms-devel] " Hendrik Visage
2002-11-06 13:55 ` Alan Cox
2002-11-06 0:36 ` [Evms-devel] " Kevin Corry
2002-11-06 1:45 ` Mike Diehl
2002-11-06 4:48 ` Alexander Viro
2002-11-06 2:54 ` Mike Diehl
2002-11-06 13:47 ` Kevin Corry
2002-11-05 23:40 ` [Evms-announce] " Andres Salomon
2002-11-05 21:29 ` Mike Diehl
2002-11-06 0:18 ` Andrew Clausen
2002-11-06 21:33 ` Matthias Andree
2002-11-07 10:37 ` Joe Thornber
2002-11-05 23:37 ` Alan Cox
2002-11-06 0:03 ` [Evms-devel] " Eff Norwood
2002-11-06 1:13 ` Rik van Riel
2002-11-06 1:41 ` Eff Norwood
2002-11-06 1:57 ` Rik van Riel
2002-11-06 2:50 ` Alexander Viro
2002-11-06 0:05 ` James H. Cloos Jr.
2002-11-06 15:21 ` Kevin Corry
2002-11-06 0:16 ` [Evms-announce] " Lars Marowsky-Bree
2002-11-06 13:55 ` Alan Cox
2002-11-06 13:59 ` Arjan van de Ven
2002-11-06 14:24 ` Jens Axboe
2002-11-06 20:46 ` H. Peter Anvin
2002-11-06 21:21 ` Alan Cox
2002-11-06 21:58 ` H. Peter Anvin
2002-11-08 18:06 ` Alan Cox
2002-11-08 19:37 ` H. Peter Anvin
2002-11-06 15:08 ` Kevin Corry [this message]
2002-11-07 20:24 ` Christoph Hellwig
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=02110609084300.06245@boiler \
--to=corryk@us.ibm.com \
--cc=evms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@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