[PATCH 3/4] usbip tools: use per vhci_hcd controller attributes

From: Salvador Fandiño Now every vhci_hcd device is controlled by its own sysfs attributes (before all of them were controlled by vhci_hcd.0 attributes). This patch addapts the usbip tools to use the new interface through libusbip. The user visible changes are as follows: - The files containing

[PATCH 1/4] usbip: make vhci_hcd.* objects independent of vhci_hcd.0

From: Salvador Fandiño The usbip VHCI layer supports multiple "vhci_hcd" devices, every one emulating both a high speed and a super speed USB hub. These devices are exposed in sysfs as "vhci_hcd.0", "vhci_hcd.1", etc. But instead of controlling then by attributes inside their respective director

[PATH 0/4] usbip: make vhci_hcd.* objects independent of vhci_hcd.0

Let me start by explaining the problem that have motivated me to write this patches: I work on the QVD, a virtual desktop platform for Linux. This software runs Linux desktops (i.e. XFCE, KDE) and their applications inside LXC containers, and makes then available through the network to remote user

[PATCH 4/4] config: make USB_MAXBUS configurable and adjust VHCI_NR_HCS top limit

From: Salvador Fandiño The maximum number of USB host controllers supported by the kernel had a hard-coded limit of 64. In some scenarios that limit may be not enough. For instance, in my particular case, I have systems with thousands of containers running and would like to provide a VHCI (USBIP

[PATCH 2/4] libusbip: use per vhci_hcd controller attributes

From: Salvador Fandiño Now every vhci_hcd device is controlled by its own sysfs attributes (before all of them were controlled by vhci_hcd.0 attributes). This patch addapts libusbip to this new interface. Before this patch the library did not provide any mean to access a specific vhci_hcd device