Difference between revisions of "Blktap3"
From Xen
(Created page with "(page under construction) blktap3 is an improved version of blktap2. The main difference between blktap2 and blktap3 is that the tapdisk process running in dom0 is directly conn…") |
Lars.kurth (talk | contribs) (Adding categories) |
||
| Line 1: | Line 1: | ||
| − | + | {{TODO|page under construction}} |
|
blktap3 is an improved version of blktap2. The main difference between blktap2 and blktap3 is that the tapdisk process running in dom0 is directly connected to blkfront, rendering blkback useless. The advantage of this approach is improved performance since requests do not have to pass through the dom0 kernel. |
blktap3 is an improved version of blktap2. The main difference between blktap2 and blktap3 is that the tapdisk process running in dom0 is directly connected to blkfront, rendering blkback useless. The advantage of this approach is improved performance since requests do not have to pass through the dom0 kernel. |
||
| Line 6: | Line 6: | ||
Need to implement support for HVM VMs, PV pugrub VMs. |
Need to implement support for HVM VMs, PV pugrub VMs. |
||
| + | |||
| + | [[Category:Xen]] |
||
| + | [[Category:Developers]] |
||
Revision as of 08:17, 1 June 2012
|
To Do:
page under construction |
blktap3 is an improved version of blktap2. The main difference between blktap2 and blktap3 is that the tapdisk process running in dom0 is directly connected to blkfront, rendering blkback useless. The advantage of this approach is improved performance since requests do not have to pass through the dom0 kernel.
blktap3 in under heavy development; it will soon be sent as a patch in xen-devel. blktap3 seems to work on PV VMs without pygrub.
Need to implement support for HVM VMs, PV pugrub VMs.
