Displaying 3 results from an estimated 3 matches for "blktap_mmap_region_size".
2012 Mar 06
0
Livelock induced failure in blktap2.
...ed.
We tracked the problem down to what appears to be a livelock related
to the unmapping of the ring memory by the tapdisk2 process. Most
specificaly the following fragment in
tapdisk-vbc:tapdisk_vbd_detach():
if (vbd->ring.mem > 0)
munmap(vbd->ring.mem, psize * BLKTAP_MMAP_REGION_SIZE);
xl sends a DETACH request to the tapdisk2 process which results in the
execution of the the munmap function call and what appears to be a
livelock.
xl times out its select() call waiting for the DETACH response from
tapdisk2 and errors out resulting in tap_ctl_free not being call for
the minor....
2008 Mar 10
12
[RFC][PATCH] Use ioemu block drivers through blktap
When I submitted the qcow2 patch for blktap, suggestions came up that
the qemu block drivers should be used also for blktap to eliminate the
current code duplication in ioemu and blktap.
The attached patch adds support for a tap:ioemu pseudo driver. Devices
using this driver won''t use tapdisk (containing the code duplication)
any more, but will connect to the qemu-dm of the domain. In
2013 Jul 15
21
[PATCH 00 of 21 RESEND] blktap3/drivers: Introduce tapdisk server.
This patch series copies the core of the tapdisk process from blktap2, with
updates coming from blktap2.5.
Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>