From: Rob Landley <rob@landley.net>
To: Christoph Lameter <cl@linux.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Gilad Ben-Yossef <gilad@benyossef.com>,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [RFC] Restrict kernel spawning of threads to a specified set of cpus.
Date: Tue, 10 Sep 2013 02:39:16 -0500 [thread overview]
Message-ID: <1378798756.8385.24@driftwood> (raw)
In-Reply-To: <00000140efbcb701-c26320b3-f434-4538-bc80-8e92fed6f303-000000@email.amazonses.com> (from cl@linux.com on Thu Sep 5 15:07:37 2013)
On 09/05/2013 03:07:37 PM, Christoph Lameter wrote:
> I am not sure how to call this kernel option but we need something
> like
> that. I see drivers and the kernel spawning processes on the nohz
> cores.
> The name kthread is not really catching the purpose.
Can't you just use the CPU affinity of PID 1 for this? Since it's a
process that's always there and already has a mask and all. No need for
a new interface...
Rob
next prev parent reply other threads:[~2013-09-10 17:33 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 20:07 [RFC] Restrict kernel spawning of threads to a specified set of cpus 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 [this message]
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
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=1378798756.8385.24@driftwood \
--to=rob@landley.net \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=fweisbec@gmail.com \
--cc=gilad@benyossef.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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.