public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: "Stefan Richter" <stefanr@s5r6.in-berlin.de>,
	"Cornelia Huck" <cornelia.huck@de.ibm.com>,
	"Adrian Bunk" <bunk@stusta.de>, "david@lang.hm" <david@lang.hm>,
	"David Miller" <davem@davemloft.net>,
	"bunk@stusta.de; Duncan Sands" <duncan.sands@math.u-psud.fr>,
	"Phillip Susi" <psusi@cfl.rr.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] driver core: multithreaded probing - more parallelism control
Date: Sun, 24 Jun 2007 00:06:02 -0700	[thread overview]
Message-ID: <20070624070601.GB24941@kroah.com> (raw)
In-Reply-To: <1182373258.30574.30.camel@caritas-dev.intel.com>

On Wed, Jun 20, 2007 at 09:00:58PM +0000, Huang, Ying wrote:
> Hi,
> 
> This is a new version of multithreaded probing patch, with more
> parallelism control added.
> 
> There are more control over which devices and drivers will be probed
> parallelized or serially. For example, in IEEE1394 subsystem, the
> different "units" in one "node" can be probed serially while the
> different "nodes" can be probed parallelized.
> 
> The number of threads can be controlled through a kernel command line
> parameters.
> 
> The patch is against 2.6.22-rc5. The "wait_for_probes" function in the
> patch comes from the original multithreaded probing patch. If I need do
> anything because of it, please let me know.
> 
> Any comment is welcome.

I'm still not convinced that we need to add this kind of complexity to
the driver core, instead of just letting the individual driver
subsystems do this, if they want to do it.

Especially as no subsystem wants to do this today :)

thanks,

greg k-h

  parent reply	other threads:[~2007-06-24  8:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1182373258.30574.30.camel@caritas-dev.intel.com>
2007-06-20 15:09 ` [PATCH] driver core: multithreaded probing - more parallelism control Stefan Richter
2007-06-20 15:14   ` Stefan Richter
2007-06-21  9:38   ` Huang, Ying
2007-06-21  8:49     ` Stefan Richter
2007-06-21 13:51       ` Huang, Ying
2007-06-21 16:21         ` Stefan Richter
2007-06-22  9:52           ` Huang, Ying
2007-07-03 15:04             ` Cornelia Huck
2007-06-24  7:06 ` Greg KH [this message]
2007-06-24  9:38   ` Stefan Richter
2007-06-24 15:04   ` [PATCH] driver core: multithreaded probing - more parallelismcontrol Huang, Ying
2007-06-25  8:16     ` Greg KH
2007-07-03  9:33       ` Cornelia Huck
2007-06-21 10:17 [PATCH] driver core: multithreaded probing - more parallelism control Huang, Ying

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=20070624070601.GB24941@kroah.com \
    --to=greg@kroah.com \
    --cc=bunk@stusta.de \
    --cc=cornelia.huck@de.ibm.com \
    --cc=davem@davemloft.net \
    --cc=david@lang.hm \
    --cc=duncan.sands@math.u-psud.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psusi@cfl.rr.com \
    --cc=stefanr@s5r6.in-berlin.de \
    --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