From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
xen-devel@lists.xensource.com, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
cyliu@suse.com, David Vrabel <david.vrabel@citrix.com>,
boris.ostrovsky@oracle.com
Subject: Re: [Xen-devel] [PATCH 3/4] usb: Introduce Xen pvUSB backend
Date: Fri, 6 Mar 2015 12:59:44 +0200 [thread overview]
Message-ID: <20150306105944.GK32543@reaktio.net> (raw)
In-Reply-To: <1425480393.25940.181.camel@citrix.com>
On Wed, Mar 04, 2015 at 02:46:33PM +0000, Ian Campbell wrote:
> On Wed, 2015-03-04 at 15:41 +0100, Juergen Gross wrote:
> > On 03/04/2015 03:29 PM, Ian Campbell wrote:
> > > On Wed, 2015-03-04 at 14:19 +0000, David Vrabel wrote:
> > >> On 04/03/15 14:09, Juergen Gross wrote:
> > >>>
> > >>> The main question whether it is worth to consider this alternative is
> > >>> the performance aspect. Does anyone have an idea which USB devices would
> > >>> typically be used via pvusb? I'd suspect memory sticks and USB disks
> > >>> and perhaps webcams being the most performance relevant ones. Is an
> > >>> additional copy operation of user data acceptable here?
> > >>
> > >> I have no idea. We (XenServer) have no use cases at all for USB device
> > >> passthrough.
> > >
I've seen XenServer customers asking for USB passthru functionality on IRC channels..
> > > My gut feeling is that for USB 1 and 2 the bus itself isn't fast enough
> > > that anyone would care. qdisk has acceptable for disks, so it's probably
> > > ok for usb too.
> >
> > While I can accept the bus speed reasoning, I doubt qdisk is copying
> > data between user and kernel space under normal circumstances. I think
> > disk I/Os are done using DMA to/from the user buffer directly.
>
> I thought there was at least one copy on the datapath with qdisk,
> wherever it is. But I don't know for sure.
>
> > > For usb 3 onwards, well, maybe when we care about those we'll decide
> > > that a kernel space driver is needed, but for now it seems like
> > > userspace would be ok.
> >
> > Do you have another feeling about the probability of a need to do usb 3?
> > If it is already on the horizon I wouldn't want to do the user space
> > backend now and the kernel one next year. :-)
>
> Well, what is *your* use case for USB passthru? I don't actually have
> one myself.
>
> I'd speculate that people are more interested in passing in
> low/medium/high speed devices rather than the superfast usb3 disks etc.
> But I have no reason to back that up.
>
People seem to ask/need USB passthru support for various use cases
including passing thru: webcams, video grabbers, printers, mobile broadband modems,
copy protection dongles, gaming controllers, you name it..
-- Pasi
next prev parent reply other threads:[~2015-03-06 11:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 13:35 [PATCH 0/4] xen, usb: support pvUSB drivers Juergen Gross
2015-02-26 13:35 ` [PATCH 1/4] usb: Add Xen pvUSB protocol description Juergen Gross
2015-02-26 13:35 ` [PATCH 2/4] usb: Introduce Xen pvUSB frontend Juergen Gross
2015-02-26 14:09 ` Oliver Neukum
2015-02-26 13:35 ` [PATCH 3/4] usb: Introduce Xen pvUSB backend Juergen Gross
2015-03-02 11:39 ` [Xen-devel] " David Vrabel
2015-03-04 13:31 ` Juergen Gross
2015-03-04 13:41 ` Ian Campbell
2015-03-04 13:45 ` Juergen Gross
2015-03-04 13:53 ` David Vrabel
2015-03-04 14:09 ` Juergen Gross
2015-03-04 14:19 ` David Vrabel
2015-03-04 14:29 ` Ian Campbell
2015-03-04 14:41 ` Juergen Gross
2015-03-04 14:43 ` Peter Stuge
2015-03-04 14:46 ` Ian Campbell
2015-03-06 10:59 ` Pasi Kärkkäinen [this message]
2015-03-06 12:52 ` Austin S Hemmelgarn
2015-03-04 15:27 ` Greg KH
2015-03-04 15:31 ` Juergen Gross
2015-02-26 13:35 ` [PATCH 4/4] xen: add Xen pvUSB maintainer Juergen Gross
2015-02-26 17:25 ` Konrad Rzeszutek Wilk
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=20150306105944.GK32543@reaktio.net \
--to=pasik@iki.fi \
--cc=boris.ostrovsky@oracle.com \
--cc=cyliu@suse.com \
--cc=david.vrabel@citrix.com \
--cc=gregkh@linuxfoundation.org \
--cc=ian.campbell@citrix.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
/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
all inboxes | Powered by JetHome®