linux-kernel - Re: [Patch 3/3] Driver core: Per-subsystem multithreaded probing.

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

Date:	Mon, 16 Oct 2006 17:45:04 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Duncan Sands <duncan.sands@...h.u-psud.fr>
cc:	Cornelia Huck <cornelia.huck@...ibm.com>,
	Greg K-H <greg@...ah.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Patch 3/3] Driver core: Per-subsystem multithreaded probing.

On Mon, 16 Oct 2006, Duncan Sands wrote:

> > That's not quite true.  You could acquire dev->parent->sem always, just to
> > be certain.  However USB shouldn't use this form of multithreaded probing
> > in any case; it should instead use multiple threads for khubd.
> 
> Is anyone working on this (multiple threads for khubd)?

Not as far as I know.  It should be trivial, though.  Just start several 
threads instead of only one during initialization, and stop them all 
during cleanup.  And have the threads use a wait queue instead of calling
wait_event_interruptible().

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/