From: Juergen Gross <jgross@suse.com>
To: George Dunlap <dunlapg@umich.edu>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: pvUSB backend performance
Date: Mon, 29 Jun 2015 15:36:28 +0200 [thread overview]
Message-ID: <559149DC.8000708@suse.com> (raw)
In-Reply-To: <CAFLBxZaV=p6GzbFCaXDFD82JNRyBw3UzctaDC11p+gtk3qAMcA@mail.gmail.com>
On 06/29/2015 03:22 PM, George Dunlap wrote:
> On Wed, Jun 24, 2015 at 1:06 PM, Juergen Gross <jgross@suse.com> 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?
>
> Just to be clear, you mean having qemu act as a pvusb backend (a la
> qdisk), not emulated, is that correct?
Yes.
> I don't actually understand your question -- is the overhead
> acceptable for what?
Acceptable for the decision to build the backend in qemu only. When I
posted the first draft of my kernel backend to lkml the question was
raised why I couldn't do this in userland via libusb.
> I think in an ideal world the toolstack will use the kernel backend if
> it's available, and fall back to a qemu backend if it's not available.
In case the performance is regarded to be sufficient I won't retry to
push a kernel backend. So there will be none in the near future.
If the performance is not good enough I'll give the kernel backend
another try. If it's being accepted I probably won't do the qemu one.
Juergen
next prev parent reply other threads:[~2015-06-29 13: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
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 [this message]
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=559149DC.8000708@suse.com \
--to=jgross@suse.com \
--cc=dunlapg@umich.edu \
--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.