From: Greg KH <greg@kroah.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: PATCH: Multiprobe sanitizer
Date: Wed, 16 Aug 2006 15:26:33 -0700 [thread overview]
Message-ID: <20060816222633.GA6829@kroah.com> (raw)
In-Reply-To: <1155746538.24077.371.camel@localhost.localdomain>
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
next prev parent reply other threads:[~2006-08-16 22:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 16:42 PATCH: Multiprobe sanitizer Alan Cox
2006-08-16 22:26 ` Greg KH [this message]
2006-08-17 0:36 ` Alan Cox
2006-08-17 6:57 ` Benjamin Herrenschmidt
2006-08-17 7:00 ` Arjan van de Ven
2006-08-17 8:41 ` Alan Cox
2006-08-17 9:24 ` Benjamin Herrenschmidt
2006-08-17 12:00 ` Greg KH
2006-08-17 12:12 ` Benjamin Herrenschmidt
2006-08-17 12:22 ` Greg KH
2006-08-17 12:37 ` Benjamin Herrenschmidt
2006-08-17 13:04 ` Arjan van de Ven
2006-08-17 13:10 ` Benjamin Herrenschmidt
2006-08-17 15:44 ` Greg KH
2006-08-17 14:43 ` Olaf Hering
2006-08-17 15:42 ` Greg KH
2006-08-17 11:58 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060816222633.GA6829@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox