Re: [Xen-devel] [PATCH 0 of 6] dm-userspace xen integration

["Christian Limpach" <christian.limpach@xxxxxxxxx>]

On 8/21/06, Ryan Grimm <grimm@xxxxxxxxxx> wrote:
> In June, Dan Smith posted a patch to add dm-userspace to the -xen kernel*.
> Since then, an io completion notification mechanism for metadata writing has
> been added*.  The kernel module, along with the the tools, consistently pass
> fsstress and dbench tests on both x86_64 and x86_32.
>
> These patches integrate dm-userspace into the xen tree and allow a cow domain
> to be created.  Hopefully some people can start experimenting with it and we
> look forward to hearing some feedback.
Has this been posted to the devicemapper list?  I think someone
mentioned it had been, could you post a reference to any follow-up
discussion?  Is there clear indication that this will be picked up by
devicemapper because I don't think we'll want to have to maintain this
in-tree forever.

> Cowd and its associated plugins are a bit rough right now, but they work, and
> we plan on smoothing things out in the near future.
>
> This patch is broken up into 6 parts:
>
> [1/6]: A patch to the xen kernel in the patches/ directory.  Also the default
> config files will build dm_userspace as a module.
>
> [2/6]: Adds the base for cowd, the userspace tool, to the tools directory.
This needs to be changed to fail gracefully if the auto* tools are not
installed.
Is the use of auto* tools absolutely necessary?  Could we checkin the
generated files as well?

Also, I think the tools/Makefile could do with a bit of cleanup where
we define %-build, %-install and %-clean targets which do the default
action and then override them with specific actions for ioemu and I
guess cowd.

> [3/6]: Adds internal libdmu support to cowd
Is this there because libdevmapper doesn't support this yet?  Is there
any version of libdevmapper which supports this yet?

> [4/6]: The dscow plugin for cowd
>
> [5/6]: The qcow plugin for cowd
>
> [6/6]: A script to start the dm-userspace backend as well as an xm example
> configuration file.
I don't think an extra example config file is needed for a single line
change.  Just add the example to the existing config files.

Does this work for qemu domains?  If so how, if not, what are your
plans to make it work for qemu domains?

    christian

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel