[PATCH v1 0/2] usbip: event handler as one thread

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear all,

In existing implementation, event kernel threads are created for each 
port. The functions of the threads are closing connection and error 
handling so they don't have not so many events to handle. There' no 
need to have thread for each port.

BEFORE) vhci side - VHCI_NPORTS(8) threads are created.
$ ps aux | grep usbip
root     10059  0.0  0.0      0     0 ?        S    17:06   0:00 
[usbip_eh]
root     10060  0.0  0.0      0     0 ?        S    17:06   0:00 
[usbip_eh]
root     10061  0.0  0.0      0     0 ?        S    17:06   0:00 
[usbip_eh]
root     10062  0.0  0.0      0     0 ?        S    17:06   0:00 
[usbip_eh]
root     10063  0.0  0.0      0     0 ?        S    17:06   0:00 
[usbip_eh]
root     10064  0.0  0.0      0     0 ?        S    17:06   0:00 
[usbip_eh]
root     10065  0.0  0.0      0     0 ?        S    17:06   0:00 
[usbip_eh]
root     10066  0.0  0.0      0     0 ?        S    17:06   0:00 
[usbip_eh]

BEFORE) stub side - threads will be created every bind operation.
$ ps aux | grep usbip
root      8368  0.0  0.0      0     0 ?        S    17:56   0:00 
[usbip_eh]
root      8399  0.0  0.0      0     0 ?        S    17:56   0:00 
[usbip_eh]

This series of patches put event threads of stub and vhci driver as one 
workqueue.

AFTER) only one event threads in each vhci and stub side.
$ ps aux | grep usbip
root     10457  0.0  0.0      0     0 ?        S<   17:47   0:00 
[usbip_event]

*** BLURB HERE ***

Nobuo Iwata (2):
  usbip: modifications to event handler
  usbip: modifications to drivers using event handler

 drivers/usb/usbip/stub_dev.c     |   3 +-
 drivers/usb/usbip/usbip_common.c |   7 ++
 drivers/usb/usbip/usbip_common.h |   4 +-
 drivers/usb/usbip/usbip_event.c  | 168 +++++++++++++++++++++++--------
 4 files changed, 137 insertions(+), 45 deletions(-)

-- 
2.1.0

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux