On 05/06/13 10:48, Hans de Goede wrote:
Due to various unfortunate reasons we cannot reliable detect a guest
cancelling a packet as soon as it happens, instead we detect cancels
with some delay.
When packets are handled async, and we directly pass the guest memory for
the packet to the
Due to various unfortunate reasons we cannot reliable detect a guest
cancelling a packet as soon as it happens, instead we detect cancels
with some delay.
When packets are handled async, and we directly pass the guest memory for
the packet to the usb-device as iovec, this means that the
Hi,
+if (max_len = sizeof(async-static_buf)) {
+async-buf = async-static_buf;
+} else {
+async-buf = g_malloc(max_len);
+}
Do we need this? I think we should simply make the static buffer big
enough for the maximum allowed packet size (isn't that big on usb
Hi,
On 04/26/2013 02:32 PM, Gerd Hoffmann wrote:
Hi,
+if (max_len = sizeof(async-static_buf)) {
+async-buf = async-static_buf;
+} else {
+async-buf = g_malloc(max_len);
+}
Do we need this? I think we should simply make the static buffer big
enough for the
Due to various unfortunate reasons we cannot reliable detect a guest
cancelling a packet as soon as it happens, instead we detect cancels
with some delay.
When packets are handled async, and we directly pass the guest memory for
the packet to the usb-device as iovec, this means that the
