lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54F71983.6070708@suse.com>
Date:	Wed, 04 Mar 2015 15:41:07 +0100
From:	Juergen Gross <jgross@...e.com>
To:	Ian Campbell <ian.campbell@...rix.com>,
	David Vrabel <david.vrabel@...rix.com>
CC:	linux-kernel@...r.kernel.org, xen-devel@...ts.xensource.com,
	konrad.wilk@...cle.com, boris.ostrovsky@...cle.com,
	linux-usb@...r.kernel.org, gregkh@...uxfoundation.org,
	cyliu@...e.com
Subject: Re: [Xen-devel] [PATCH 3/4] usb: Introduce Xen pvUSB backend

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.
>
> 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.

> 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. :-)


Juergen
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ