From: Greg KH <gregkh@suse.de>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: [RFC PATCH] Multi-threaded device probing
Date: Wed, 26 Jul 2006 00:24:52 -0700 [thread overview]
Message-ID: <20060726072452.GB6249@suse.de> (raw)
In-Reply-To: <44C69819.8080908@superbug.co.uk>
On Tue, Jul 25, 2006 at 11:15:53PM +0100, James Courtier-Dutton wrote:
> 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.
>
> What happens about the logging?
Nothing, it works just fine. A little messy perhaps, but it's all
there. I don't see the problem here...
> Surely one would want the output from one probe to be output into the
> log as a block, and not mix the output from multiple simultaneous probes.
Why not? Each subsystem already uses the dev_printk() for the most part
for their logging messages, so it's easy to figure out what is going on.
thanks,
greg k-h
next prev parent reply other threads:[~2006-07-26 7:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 20:30 [RFC PATCH] Multi-threaded device probing Greg KH
2006-07-25 21:09 ` Alexey Dobriyan
2006-07-25 21:27 ` Greg KH
2006-07-25 21:27 ` H. Peter Anvin
2006-07-25 22:00 ` Dmitry Torokhov
2006-07-26 7:28 ` Greg KH
2006-07-25 22:15 ` James Courtier-Dutton
2006-07-26 0:08 ` Stefan Richter
2006-07-26 7:27 ` Greg KH
2006-07-26 7:24 ` Greg KH [this message]
2006-07-25 22:57 ` Keshavamurthy Anil S
2006-07-26 7:22 ` Greg KH
2006-07-26 0:34 ` Stefan Richter
2006-07-26 7:31 ` Greg KH
2006-07-26 11:29 ` Matthew Wilcox
2006-07-26 16:16 ` Greg KH
2006-07-26 16:42 ` Matthew Wilcox
2006-07-26 16:46 ` Greg KH
2006-07-27 0:02 ` Arnd Bergmann
2006-07-27 0:20 ` 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=20060726072452.GB6249@suse.de \
--to=gregkh@suse.de \
--cc=James@superbug.co.uk \
--cc=greg@kroah.com \
--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