From: Ryan Grimm <grimm@us.ibm.com>
Subject: [PATCH 0 of 6] dm-userspace xen integration patches
Date: Fri, 25 Aug 2006 16:23:44 -0500
Message-ID: <20060825212344.GA31071@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Xen Devel <xen-devel@lists.xensource.com>
Cc: Dan Smith <danms@us.ibm.com>
List-Id: xen-devel@lists.xenproject.org

Here are our latest dm-userspace-xen integration patches.  A few things have
changed since our last patch:  synchronous metadata flushing and block-dmu
script updates to avoid xend races, a makefile change to ensure we check for
autotools, and a change to the dscow creation tool to allow for large dscow
files.

I'd like to point out that having dm-userspace integrated into xen allows a
user to quickly and easily specify a base device and where they'd like to store
the changes.  All they have to do is change one line in their xm config file,
and they're good to go.

Our main focus here is really block devices, such as LVMS, nbd, iSCSI.  We do
support file-backed images as an experimental feature and encourage using it
with care since there are some potential issues with the current loop driver.

Comments are much appreciated.

--
Thanks,
Ryan Grimm
IBM Linux Technology Center