From: Juergen Gross <jgross@suse.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: pvUSB backend performance
Date: Wed, 24 Jun 2015 14:06:02 +0200 [thread overview]
Message-ID: <558A9D2A.2020006@suse.com> (raw)
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?
BTW: I managed not to have to copy the I/O-data in the backend, it is
just mapped into user space and then given to the USB framework of qemu.
I think it will be copied there, but changing this will require a lot
of work...
Juergen
next reply other threads:[~2015-06-24 12:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 12:06 Juergen Gross [this message]
2015-06-24 13:57 ` pvUSB backend performance Konrad Rzeszutek Wilk
2015-06-25 3:36 ` Juergen Gross
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=558A9D2A.2020006@suse.com \
--to=jgross@suse.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 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.