All of lore.kernel.org
 help / color / mirror / Atom feed
From: Til Obes <til@obes.name>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Performance of USB2.0
Date: Thu, 05 Jan 2012 17:29:37 +0100	[thread overview]
Message-ID: <je4j5o$at3$1@dough.gmane.org> (raw)
In-Reply-To: <4EAFBDBF.3070109@redhat.com>

Hello.

Am 01.11.2011 10:37, schrieb Gerd Hoffmann:
> I think the main issue here is that we don't do buffering / pipelining
> for bulk transfers at the moment.  We grab a single transfer request
> from the guest, pass it to the kernel, when it is done pass it back to
> the guest, then look look for the next one.  Instead we could queue up
> all transfer requests from the guest to the kernel, which would give a
> noticable better throughput.  The qemu usb subsystem can't handle that
> (yet).  Fixing that is one the TODO list though.

Any news about this topic?

Regards Til

      parent reply	other threads:[~2012-01-05 16:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31  9:27 [Qemu-devel] Performance of USB2.0 Til Obes
2011-10-31 12:46 ` Hans de Goede
2011-10-31 13:37   ` Til Obes
2011-10-31 15:22     ` Hans de Goede
2011-11-01  9:37   ` Gerd Hoffmann
2011-11-01 13:42     ` Til Obes
2012-01-05 16:29     ` Til Obes [this message]

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='je4j5o$at3$1@dough.gmane.org' \
    --to=til@obes.name \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.