linux-kernel - Re: [linux-usb-devel] usbfs2: Why asynchronous I/O?

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: <20070227002023.GA13099@kroah.com>
Date:	Mon, 26 Feb 2007 16:20:23 -0800
From:	Greg KH <greg@...ah.com>
To:	Sarah Bailey <saharabeara@...il.com>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	usb-hacking@...s.cs.pdx.edu,
	USB development list <linux-usb-devel@...ts.sourceforge.net>
Subject: Re: [linux-usb-devel] usbfs2: Why asynchronous I/O?

On Mon, Feb 26, 2007 at 12:54:31AM -0800, Sarah Bailey wrote:
> Yes, a sane interface to the USRP was one of the main motivations for
> the new USB filesystem.  It remains to be seen whether we need a
> non-standard interface like io_submit, or whether threads with blocking
> I/O is fast enough and has the right semantics.

So, just for the sake of argument, how would one submit multiple urbs to
a single endpoint to ensure that the pipe is full with blocking I/O?
Would they have to:

  - open endpoint
  - create thread 1
  - create thread 2
  - create thread 3
  - create thread 4
  - send first packet to thread 1 to have it write to the endpoint.
  - send next packet to thread 2 to have it write to the endpoint.
  ...  and so on?

This seems very "hard" on userspace for something as simple as "I want
to send this data stream to the USB device as fast as is possible".

With async I/O you can just:
  - open endpoint
  - send first packet to endpoint with async write
  - send second packet to endpoint
  ... and so on


I'm all for using threads in userspace, as they are good ideas and very
powerful, but for a single data stream, they really seem like a complex
solution.

thanks,

greg k-h
-
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/