Lines Matching refs:disk
11 The blktap2 userspace toolkit provides a user-level disk I/O
22 - Metadata disk formats such as Copy-on-Write, encrypted disks, sparse
30 - Per-disk handler processes enable easier userspace policing of block
31 resources, and process-granularity QoS techniques (disk scheduling
43 Working in conjunction with the kernel blktap2 driver, all disk I/O
45 memory interface) through a character device. Each active disk is
46 mapped to an individual device node, allowing per-disk processes to
51 code. We provide a simple, asynchronous virtual disk interface that
52 makes it quite easy to add new disk implementations.
54 As of June 2009 the current supported disk formats are:
57 - Fast sharable RAM disk between VMs (requires some form of
81 The userspace disk agent is configured to start automatically via xend
87 disk = ['tap:tapdisk:aio:<FILENAME>,sda1,w']
111 disk = ['tap:tapdisk:vhd:<VHD FILENAME>,sda1,w']
120 perform a live snapshot of a qcow disk. VHD files can use the
174 demonstrate, I will create a disk called "mynewdisk", you can name
182 2) Claim one of the unused disk type numbers, take care to observe the
201 A few words about what these mean. The first field must be the disk
203 describing your disk, and may contain any relevant info. The third
204 field is the name of your disk as will be used by the tapdisk2 utility
205 and xend (for example tapdisk2 -n mynewdisk:/path/to/disk.image, or in
214 4) Add a reference to your disk info structure (from step (3)) to the
220 5) Modify the xend python scripts. You need to add your disk name to
226 And add your disk to the "blktap_disk_types" array near the top of
274 disk. You need to fill this out. By convention this is done with a
284 disk.
290 depend on your disk, but you should do exactly one of-