From: Andrew Morton <akpm@linux-foundation.org>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: fweisbec@gmail.com, mingo@elte.hu, linux-kernel@vger.kernel.org,
oleg@redhat.com, travis@sgi.com, a.p.zijlstra@chello.nl,
rusty@rustcorp.com.au
Subject: Re: + work_on_cpu-rewrite-it-to-create-a-kernel-thread-on-demand.patch added to -mm tree
Date: Thu, 12 Feb 2009 14:23:14 -0800 [thread overview]
Message-ID: <20090212142314.9ab6ad6f.akpm@linux-foundation.org> (raw)
In-Reply-To: <m17i3vz4lp.fsf@fess.ebiederm.org>
On Thu, 12 Feb 2009 14:13:06 -0800
ebiederm@xmission.com (Eric W. Biederman) wrote:
>
> I should follow up and say that the reason I care right now, is I am
> digging into pci hotplug. One of the issues I'm fighting is that
> currently I appear to need a dedicated kernel thread for each pci
> hotplug slot. It gets easy to deadlock the kernel hotplugging
> a hotplug controller otherwise.
>
um, ok, if you say so...
I'd have thought that a short-lived kernel thread would be appropriate,
if poss. Physical hotplug of a PCI device isn't a high-frequency
operation.
The new-fangled work_on_cpu() could do that, or maybe the new-fangled
kernel/async.c code.
next prev parent reply other threads:[~2009-02-12 22:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 10:58 + work_on_cpu-rewrite-it-to-create-a-kernel-thread-on-demand.patch added to -mm tree akpm
2009-02-03 12:11 ` Ingo Molnar
2009-02-03 16:58 ` Frédéric Weisbecker
2009-02-03 19:25 ` Andrew Morton
2009-02-04 3:58 ` Rusty Russell
2009-02-04 4:16 ` Andrew Morton
2009-02-04 10:46 ` Rusty Russell
2009-02-12 20:38 ` Eric W. Biederman
2009-02-12 20:48 ` Andrew Morton
2009-02-12 20:48 ` Andrew Morton
2009-02-12 22:08 ` Eric W. Biederman
2009-02-12 22:13 ` Eric W. Biederman
2009-02-12 22:23 ` Andrew Morton [this message]
2009-02-12 23:04 ` Eric W. Biederman
2009-02-12 22:20 ` Andrew Morton
2009-02-12 22:20 ` Andrew Morton
2009-02-13 21:21 ` Rusty Russell
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=20090212142314.9ab6ad6f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=ebiederm@xmission.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=travis@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.