WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] [PATCH 0 of 7] blktap2: The tap-ctl userspace control utilit

To: Xen <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH 0 of 7] blktap2: The tap-ctl userspace control utility and library
From: Daniel Stodden <daniel.stodden@xxxxxxxxxx>
Date: Mon, 07 Jun 2010 21:54:47 -0000
Delivery-date: Mon, 07 Jun 2010 14:55:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mercurial-patchbomb/1.4.3
Hi.

Apart from removing some dead code and tidying up tapdisk-vbd a
little, the bigger introduces our new tap-ctl utility code.

The code aims to be a complete replacement for the original blktap2
control path, run through sysfs. Fully implemented in userspace, all
tapdisks now gained a small IPC layer on top of Unix domain sockets.

Sample usage:

# tap-ctl allocate
/dev/xen/blktap-2/tapdev0

# tap-ctl spawn
tapdisk spawned with pid 4168

# tap-ctl list
    4168  -    -          - -
       -  0    -          - -

# tap-ctl attach -p 4168 -m 0
# tap-ctl list
    4168  0    0          - -

# tap-ctl open -p 4168 -m 0 -a aio:/var/tmp/lenny.ext

# tap-ctl list
    4168  0    0        aio /var/tmp/lenny.ext

# tap-ctl close -p 4168 -m 0
# tap-ctl detach -p 4168 -m 0
# tap-ctl free -m 0

The above example is a bit noisy, because it's mediating between minor
number (block devices), tapdisks and tapdisk VBDs (the tapdisk I/O
queue running a bdev) in detail. 

There are shortcuts. At the same time, the low-level interface should
be general enough to stay extensible, and help accomodate some of the
more esoteric features, like shared images and/or multiple VBDs
sharing the same tapdisk.

Cheers,
Daniel

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