From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] driver core: multithreaded device matching with dependency
Date: Fri, 08 Jun 2007 16:12:36 +0200 [thread overview]
Message-ID: <466963D4.6010008@s5r6.in-berlin.de> (raw)
In-Reply-To: <9D7649D18729DE4BB2BD7B494F7FEDC2041245@pdsmsx415.ccr.corp.intel.com>
Huang, Ying wrote:
>>From: Stefan Richter [mailto:stefanr@s5r6.in-berlin.de]
>>
>>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.
>
> For subsystems specific dependency problems, a field as follow can be
> added into struct device:
>
> struct device *depend;
>
> The parallel device probing code will not do probing for the device,
> unless the device pointed by "depend" has been probed,
A bad API. Subsystems and the driver core will both traverse the trees
(usually just lists) which can be built from the depend pointers, and
the trees grow and shrink dynamically. Perhaps it would be simpler if
the subsystem would just use a mutex per group of devices which have to
be serialized.
*However*, IMO parallelized probing should be implemented in the
subsystems themselves in the first place, _not in the driver core_.
The subsystems know where parallelism is possible and safe and
effective, the driver core doesn't.
--
Stefan Richter
-=====-=-=== -==- -=---
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-06-08 14:12 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
2007-06-08 9:27 ` Huang, Ying
2007-06-08 14:12 ` Stefan Richter [this message]
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=466963D4.6010008@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=greg@kroah.com \
--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®