Re: PATCH: Multiprobe sanitizer

[Greg KH <greg@kroah.com>]

On Wed, Aug 16, 2006 at 05:42:18PM +0100, Alan Cox wrote:
> There are numerous drivers that can use multithreaded probing but having
> some kind of global flag as the way to control this makes migration to
> threaded probing hard and since it enables it everywhere and is almost
> as likely to cause serious pain as holding a clog dance in a minefield.
> 
> If we have a pci_driver multithread_probe flag to inherit you can turn
> it on for one driver at a time. 

I was thinking about this originally, but didn't want to go and modify
every PCI driver to enable it :)

But I do like your patch below that lets the options mix nicely.

> From playing so far however I think we need a different model at the
> device layer which serializes until the called probe function says "ok
> you can start another one now". That would need some kind of flag and
> semaphore plus a helper function.

What would this help out with?  Would the PCI layer (for example) handle
this "notify the core that it can continue" type logic?  Or would the
individual drivers need to be able to control it?

I'm guessing that you are thinking of this in relation to the disk
drivers, have you found cases where something like this is necessary due
to hardware constraints?

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/