[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <559AE1BE.5050906@codeweavers.com>
Date: Mon, 06 Jul 2015 15:14:54 -0500
From: Jeremy White <jwhite@...eweavers.com>
To: Oliver Neukum <oneukum@...e.com>,
Krzysztof Opasiak <k.opasiak@...sung.com>
CC: Alan Stern <stern@...land.harvard.edu>,
Hans de Goede <hdegoede@...hat.com>,
"Daniel P. Berrange" <berrange@...hat.com>,
spice-devel@...ts.freedesktop.org, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [Spice-devel] [RFC PATCH 1/1] Add a usbredir kernel module to
remotely connect USB devices over IP.
On 07/06/2015 03:20 AM, Oliver Neukum wrote:
> On Fri, 2015-07-03 at 10:51 +0200, Krzysztof Opasiak wrote:
>> Doesn't we have the same problem with functionfs/gadgetfs and
>> dummy_hcd?
>> Or with fuse?
>>
>> It's a very generic problem for all "virtualized devices" and it is
>> known for quite a long time. This is why many tutorials about swap
>> warns
>> that swap should be set up only on real block devices which are fully
>> served in kernel.
>
> Indeed. But the point is that it isn't limited to swap. As you as
> a page needs to be laundered the problem exists.
> Mmapping a file for write (non private) is enough.
I'm persuaded to avoid user space in the core design.
Anything else fundamental to usbip that should inform the design of a
usbredir driver? usbip appears to be based off a 2004 vintage of
dummy_hcd. I'll look thoughtfully at the current dummy_hcd; please let
me know if there is anything else I should consider.
Cheers,
Jeremy
--
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