From: Juergen Gross <jgross@suse.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: pvUSB backend performance
Date: Thu, 25 Jun 2015 05:36:04 +0200 [thread overview]
Message-ID: <558B7724.20402@suse.com> (raw)
In-Reply-To: <20150624135732.GC2742@l.oracle.com>
On 06/24/2015 03:57 PM, Konrad Rzeszutek Wilk wrote:
> On Wed, Jun 24, 2015 at 02:06:02PM +0200, Juergen Gross wrote:
>> Hi,
>>
>> my qemu integrated pvUSB backend is now running stable enough to do
>> some basic performance measurements. I've passed a memory-stick with
>> about 90MB of data on it to a pv-domU. Then I read all the data on
>> it with tar and looked how long this would take (elapsed time):
>>
>> in dom0: 5.2s
>> in domU with kernel backend: 6.1s
>> in domU with qemu backend: 8.2s
>>
>> So the qemu backend is about 30% slower than the kernel backend. Is
>> this acceptable?
>
> That sounds about right. I remember seeing (two years ago?) an demonstration
> by kraxel where he was doing USB camera in a guest. He pointed out
> that USB1 (which is default one in QEMU) implementation sucks as QEMU
> has to poll for the commands every time. The XHCI implementation is
> better as it has some better API, or such (-EFORGOT).
>
> Oh, this has more details:
> https://www.kraxel.org/blog/2014/03/qemu-and-usb-tablet-cpu-consumtion/
This should be no problem in my case. I'm using libusb, so there is no
host adapter emulation active in qemu.
Juergen
next prev parent reply other threads:[~2015-06-25 3:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 12:06 pvUSB backend performance Juergen Gross
2015-06-24 13:57 ` Konrad Rzeszutek Wilk
2015-06-25 3:36 ` Juergen Gross [this message]
2015-06-25 8:53 ` Dario Faggioli
2015-06-25 10:41 ` Juergen Gross
2015-06-29 13:22 ` George Dunlap
2015-06-29 13:36 ` Juergen Gross
2015-07-02 16:41 ` George Dunlap
2015-07-03 4:27 ` Juergen Gross
2015-06-29 13:46 ` David Vrabel
2015-06-29 13:53 ` Juergen Gross
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=558B7724.20402@suse.com \
--to=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.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