From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com,
Matthew Wilcox <matthew@wil.cx>
Subject: Re: [RFC PATCH] Multi-threaded device probing
Date: Wed, 26 Jul 2006 02:34:09 +0200 [thread overview]
Message-ID: <44C6B881.7030901@s5r6.in-berlin.de> (raw)
In-Reply-To: <20060725203028.GA1270@kroah.com>
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.
...
Just FYI:
1.) SCSI:
There is a patch circulating at linux-scsi which adds parallelized bus
scanning to the SCSI subsystem. I believe this cannot be built upon
parallelization by driver core. But I am not too familiar with the
subsystem facilities which this patch expands on. The patch is from
Matthew Wilcox, titled "Asynchronous target discovery".
http://marc.theaimsgroup.com/?t=115349750400001
2.) IEEE 1394:
There was brief preliminary discussion of parallelized probing for the
ieee1394 subsystem at linux1394-devel. Using driver core's
parallelization would achieve about 1/3rd of what would be desirable.
Background: After each bus reset, the 1394 core (nodemgr) has to
download part or all of the configuration ROM of attached devices to
determine their identity and capabilities. After that, either a protocol
driver probe (generic device hook), a protocol driver remove or suspend
routine (generic device hook), or a protocol driver update routine
(extra 1394 subsystem hook) is executed; depending on whether nodes were
added, removed, or in-use nodes were rediscovered. --- I.e. we better
have these subthreads provided by ieee1394/nodemgr itself.
--
Stefan Richter
-=====-=-==- -=== ==-=-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2006-07-26 0:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 20:30 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
2006-07-25 22:57 ` Keshavamurthy Anil S
2006-07-26 7:22 ` Greg KH
2006-07-26 0:34 ` Stefan Richter [this message]
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=44C6B881.7030901@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
/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
all inboxes | Powered by JetHome®