From: Mike Galbraith <bitbucket@online.de>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: Christoph Lameter <cl@linux.com>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbec@gmail.com>,
Mike Frysinger <vapier@gentoo.org>,
"linux-kernel@vger.kernel.org" <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 08:47:39 +0200 [thread overview]
Message-ID: <1378795659.6046.41.camel@marge.simpson.net> (raw)
In-Reply-To: <CAOtvUMe=jcAHXNJU_rTAAokaE4KZNUTFsHVVTTxgFW_xj8ONxg@mail.gmail.com>
On Tue, 2013-09-10 at 09:05 +0300, Gilad Ben-Yossef wrote:
> Hi,
>
> On Thu, Sep 5, 2013 at 11:07 PM, Christoph Lameter <cl@linux.com> 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.
> >
> > os_cpus=? highlatency_cpus=?
> >
>
> First off, thank you for doing this. It is very useful :-)
>
> Currently if one wishes to run a single task on an isolated CPU with
> as little interference as possible, one needs to pass
> rcu_nocbs, isolcpus, nohz_full parameters and now kthread parameter,
> all pretty much with the same values
>
> I know some people won't like this, but can we perhaps fold all these
> into a single parameter, perhaps even the existing isolcpus?
isolcpus is supposed to go away, as cpusets can isolate CPUs, and can
turn off load balancing.
-Mike
next prev parent reply other threads:[~2013-09-10 6:47 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 [this message]
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
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=1378795659.6046.41.camel@marge.simpson.net \
--to=bitbucket@online.de \
--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 \
--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