mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] driver core: multithreaded device matching with dependency
Date: Fri, 08 Jun 2007 10:57:31 +0200	[thread overview]
Message-ID: <466919FB.8080204@s5r6.in-berlin.de> (raw)
In-Reply-To: <1181300879.8064.25.camel@caritas-dev.intel.com>

Huang, Ying wrote:
> This is another solution to implement multithreaded device matching
> (probing). The device matching is delayed until all drivers are
> registered. The driver registering is executed one by one, this
> eliminates the potential of interdependency between driver. All devices
> are matched to drivers afterwards, multithreaded. The parent <->
> children relationship between devices is used as the dependency between
> devices, that is, the children devices matching will not begin until
> parent device matching finishes.

How can subsystems control multithreaded vs. singlethreaded probes?

For example, the IEEE 1394 subsystem should probe different nodes in
parallel, but different units on the same node serially.  Similar
requirements exist with other hardware.

Also, how can subsystems enable and disable multithreaded probes?

...
> +EXPORT_SYMBOL_GPL(device_match_freeze);
> +EXPORT_SYMBOL_GPL(device_match_thaw);

Their definitions lack kerneldoc comments.
-- 
Stefan Richter
-=====-=-=== -==- -=---
http://arcgraph.de/sr/

  reply	other threads:[~2007-06-08  8:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08 11:07 Huang, Ying
2007-06-08  8:57 ` Stefan Richter [this message]
2007-06-08  9:27   ` Huang, Ying
2007-06-08 14:12     ` Stefan Richter
2007-06-08 15:16       ` Huang, Ying
2007-06-09 15:57       ` Huang, Ying
2007-06-09 16:32         ` Stefan Richter
2007-06-12 10:12           ` Huang, Ying
2007-06-12 14:30             ` Stefan Richter
2007-06-14 19:12               ` 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=466919FB.8080204@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ying.huang@intel.com \
    /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®