From: Peter Zijlstra <peterz@infradead.org>
To: Christoph Lameter <cl@linux.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Gilad Ben-Yossef <gilad@benyossef.com>,
Thomas Gleixner <tglx@linutronix.de>,
Mike Frysinger <vapier@gentoo.org>,
linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [RFC] Restrict kernel spawning of threads to a specified set of cpus.
Date: Mon, 16 Sep 2013 08:02:10 +0200 [thread overview]
Message-ID: <20130916060210.GM21832@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <0000014117fb2ea3-ec97f4c4-344b-42c5-b27c-be876f723942-000000@email.amazonses.com>
On Fri, Sep 13, 2013 at 03:40:40PM +0000, Christoph Lameter wrote:
> Hmmm... usermodehelper is based on workqueues. I guess this will
> ultimately come down to modify the workqueue behavior for
> WORK_CPU_UNBOUND?
You don't need to keep it like that -- in fact I would suggest removing
that dependency and creating an extra (explicit) unbound thread spawner
that both usermodehelper and kworker can use for unbound threads.
> If WORK_CPU_UNBOUND could mean to limit process execution to the affinity
> of kthreadd then we are fine.
No, kthreadd must stay clean, if must not have any affinity nor be part
of any cgroup like thing. We must have means of spawning clean kthreads,
therefore we need to create a new parent for these special cases.
next prev parent reply other threads:[~2013-09-16 6:02 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 20:07 Christoph Lameter
2013-09-10 6:05 ` Gilad Ben-Yossef
2013-09-10 6:47 ` Mike Galbraith
2013-09-10 6:59 ` Gilad Ben-Yossef
2013-09-10 7:26 ` Mike Galbraith
2013-09-10 7:56 ` Gilad Ben-Yossef
2013-09-10 8:53 ` Mike Galbraith
2013-09-10 21:10 ` Christoph Lameter
2013-09-11 3:20 ` Mike Galbraith
2013-09-11 14:21 ` Christoph Lameter
2013-09-11 14:53 ` Mike Galbraith
2013-09-11 16:56 ` Christoph Lameter
2013-09-11 21:36 ` Frederic Weisbecker
2013-09-12 3:30 ` Mike Galbraith
2013-09-10 21:08 ` Christoph Lameter
2013-09-10 7:39 ` Rob Landley
2013-09-10 21:11 ` Christoph Lameter
2013-09-11 22:02 ` Frederic Weisbecker
2013-09-12 14:10 ` Christoph Lameter
2013-09-12 14:16 ` Frederic Weisbecker
2013-09-12 14:22 ` Christoph Lameter
2013-09-12 14:31 ` Frederic Weisbecker
2013-09-12 14:52 ` Christoph Lameter
2013-09-12 15:11 ` Frederic Weisbecker
2013-09-12 15:32 ` Christoph Lameter
2013-09-12 18:45 ` Frederic Weisbecker
2013-09-12 15:39 ` Paul E. McKenney
2013-09-12 18:35 ` Frederic Weisbecker
2013-09-12 18:51 ` Paul E. McKenney
2013-09-15 13:53 ` Gilad Ben-Yossef
[not found] ` <alpine.DEB.2.02.1309121030390.21473@gentwo.org>
2013-09-12 15:42 ` Christoph Lameter
2013-09-12 18:30 ` Frederic Weisbecker
2013-09-13 9:25 ` Peter Zijlstra
2013-09-13 13:54 ` Christoph Lameter
2013-09-13 14:40 ` Peter Zijlstra
2013-09-13 15:15 ` Christoph Lameter
[not found] ` <alpine.DEB.2.02.1309131010480.26487@gentwo.org>
2013-09-13 15:40 ` Christoph Lameter
2013-09-16 6:02 ` Peter Zijlstra [this message]
2013-09-13 13:45 ` Christoph Lameter
2013-09-13 14:04 ` Frederic Weisbecker
2013-09-13 14:25 ` Christoph Lameter
2013-09-15 13:47 ` Gilad Ben-Yossef
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=20130916060210.GM21832@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=fweisbec@gmail.com \
--cc=gilad@benyossef.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=vapier@gentoo.org \
/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
Powered by JetHome