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
| ||
|
Date: Wed, 26 Jul 2006 00:28:24 -0700 From: Greg KH <gregkh@...e.de> To: Dmitry Torokhov <dtor@...ightbb.com> Cc: linux-kernel@...r.kernel.org, greg@...ah.com Subject: Re: [RFC PATCH] Multi-threaded device probing On Tue, Jul 25, 2006 at 06:00:24PM -0400, Dmitry Torokhov wrote: > On Tuesday 25 July 2006 16:30, Greg KH wrote: > > During the kernel summit, I was reminded by the wish by some people to > > do device probing in parallel, so I created the following patch. It > > offers up the ability for the driver core to create a new thread for > > every driver<->device probe call. To enable this, the driver needs to > > have the multithread_probe flag set to 1, otherwise the "traditional" > > sequencial probe happens. > > > > Another option would be to have probing still serialized within a bus but > serviced by a separate thread. The thread can die after let's say 1 minute > inactivity timeout and respawned if needed. Yes, you can do that right now if you wish, no need to mess with the driver core. But for busses that don't want to do something like that (like USB and PCI probably will not), this option is now available. 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/
Powered by blists - more mailing lists