From: Andi Kleen <andi@firstfloor.org>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: "Reddy, Teerth" <teerth@ti.com>, pm list <linux-pm@lists.osdl.org>
Subject: Re: Use of parallel init threads for slow devices start ups?
Date: 20 Feb 2007 00:52:31 +0100 [thread overview]
Message-ID: <p73hcthemdc.fsf@bingen.suse.de> (raw)
In-Reply-To: <3B6D69C3A9EBCA4BA5DA60D9130274295B9D66@dlee13.ent.ti.com>
"Woodruff, Richard" <r-woodruff2@ti.com> writes:
>
> Does anyone want to give an opinion on forking off a parallel thread to
> handle slower devices which are not dependent?
Recent kernels have CONFIG_PCI_MULTITHREAD_PROBE. But it's considered
highly experimental for now because of unknown races.
I guess a lot of testing and fixing any bugs you hit would be welcome.
-Andi
next prev parent reply other threads:[~2007-02-19 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 17:50 Use of parallel init threads for slow devices start ups? Woodruff, Richard
2007-02-19 22:26 ` Pavel Machek
2007-02-19 23:52 ` Andi Kleen [this message]
2007-02-20 0:48 ` 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=p73hcthemdc.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=linux-pm@lists.osdl.org \
--cc=r-woodruff2@ti.com \
--cc=teerth@ti.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