From: Hans de Goede <hdegoede@redhat.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] USB: add usb network redirection support
Date: Mon, 18 Jul 2011 09:17:45 +0200 [thread overview]
Message-ID: <4E23DE19.8040205@redhat.com> (raw)
In-Reply-To: <1310973217-12242-1-git-send-email-hdegoede@redhat.com>
Hi,
Note that using this with devices where a lot of data is send to the device
(ie a usb stick and writing to it a lot) may lead to increased latencies, due
to the long missing flowcontrol support in chardev in one direction.
For those interested, my personal tree contains Amit's flowcontrol patches
ported to the latest qemu-git + a version of the usb-redir patch with
flowcontrol support:
http://cgit.freedesktop.org/~jwrdegoede/qemu/log/?h=usbredir
Regards,
Hans
next prev parent reply other threads:[~2011-07-18 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 7:13 [Qemu-devel] [PATCH] USB: add usb network redirection support Hans de Goede
2011-07-18 7:17 ` Hans de Goede [this message]
2011-07-18 9:50 ` Hans de Goede
2011-07-18 14:33 ` Gerd Hoffmann
2011-07-19 9:03 ` Hans de Goede
-- strict thread matches above, loose matches on Subject: below --
2011-07-19 9:04 Hans de Goede
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E23DE19.8040205@redhat.com \
--to=hdegoede@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).