linux-kernel - Re [patch 2/3] fastboot: turn the USB hostcontroller initcalls into async initcalls

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-next>] [day] [month] [year] [list]

Date:	Sat, 19 Jul 2008 11:25:29 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Arjan van de Ven <arjan@...radead.org>
cc:	Kernel development list <linux-kernel@...r.kernel.org>,
	USB list <linux-usb@...r.kernel.org>
Subject: Re  [patch 2/3] fastboot: turn the USB hostcontroller initcalls into
 async initcalls

On 18 July, 2008, Arjan van de Ven wrote:

> From: Arjan van de Ven <arjan@...ux.intel.com>
> Subject: [PATCH] fastboot: turn the USB hostcontroller initcalls into 
> async initcalls
> 
> the USB host controller init calls take a long time, mostly due to a
> "minimally 100 msec" delay *per port* during initialization.
> These are prime candidates for going in parallel to everything else.
> 
> The USB device ordering is not affected by this due to the
> serialized-within-eachother property of async initcalls.

Is there some reason this patch wasn't posted to the linux-usb mailing
list as well as to LKML?

Where is this "minimally 100 msec" per-port delay you refer to?  
Offhand I can't recall any such delays in the init routines.

Alan Stern

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