Displaying 4 results from an estimated 4 matches for "treq".
Did you mean:
req
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>
2012 Apr 02
23
[PATCH 00 of 18] [v2] tools: fix bugs and build errors triggered by -O2 -Wall -Werror
Changes:
tools/blktap: remove unneeded pointer dereferencing in convert_dev_name_to_num
tools/blktap: constify string arrays in convert_dev_name_to_num
tools/blktap: fix params and physical-device parsing
tools/blktap: remove unneeded pointer dereferencing from img2qcow.c
tools/blktap: remove unneeded pointer dereferencing from qcow2raw.c
tools/blktap2: fix build errors caused by Werror in
2011 Apr 06
1
Xen page sharing
...flags TD_OPEN_RDONLY and TD_OPEN_SHAREABLE are only set on level >= 1 in ''tapdisk_vbd_open_level()'' [tapdisk-vbd.c].
6. In your patch - ''tools.patch'', i could not understand why you check for this condition to hold true- ''((&vreq->req)->seg[treq.sidx].gref)'' in functions- ''__tapdisk_vbd_complete_td_request'' and ''__tapdisk_vbd_reissue_td_request'' [tapdisk-vbd.c].
I mean, is gref=0 bad?
If I keep this condition the control is never transferred to ''memshr_vbd_issue_ro_request'' o...
2013 Jul 15
6
[PATCH 0 of 6 RESEND v2] blktap3/sring: shared ring between tapdisk and the front-end
This patch series introduces the shared ring used by the front-end to pass
request descriptors to tapdisk, as well as responses from tapdisk to the
front-end. Requests from this ring end up in tapdisk''s standard request queue.
When the tapback daemon detects that the front-end tries to connect to the
back-end, it spawns a tapdisk and tells it to connect to the shared ring. The
shared