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/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
