From: Frederic Weisbecker <fweisbec@gmail.com>
To: Christoph Lameter <cl@linux.com>
Cc: Chris Metcalf <cmetcalf@ezchip.com>,
paulmck@linux.vnet.ibm.com, Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Mike Galbraith <umgwanakikbuti@gmail.com>,
Dave Jones <davej@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Oleg Nesterov <oleg@redhat.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Rik van Riel <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] nohz: Revert "nohz: Set isolcpus when nohz_full is set"
Date: Mon, 12 Oct 2015 19:50:29 +0200 [thread overview]
Message-ID: <20151012175027.GC1113@lerouge> (raw)
In-Reply-To: <alpine.DEB.2.20.1510121243300.32239@east.gentwo.org>
On Mon, Oct 12, 2015 at 12:45:08PM -0500, Christoph Lameter wrote:
> On Mon, 12 Oct 2015, Frederic Weisbecker wrote:
>
> > But yeah if you guys want to create a new parameter that gathers nohz
> > and isolcpus I think we can.
>
> Could we also add the rcu settings?
Yeah, those are implied by nohz_full anyway.
Now nohz_full shouldn't imply anything else than nohz but I'm not sure
I can change that. Kernel parameters are ABIs of some sort.
Ideally we should have something like cpu_isolation= which implies everything.
>
> > task_isolation is really just about tasks so it should be another name.
>
> no_os_cpus?
>
> os_free_cpus?
No, we can still do syscalls :-)
But noise_free_cpus= ?
next prev parent reply other threads:[~2015-10-12 17:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 15:21 [PATCH] nohz: Revert "nohz: Set isolcpus when nohz_full is set" Frederic Weisbecker
2015-10-12 15:32 ` Paul E. McKenney
2015-10-12 16:20 ` Frederic Weisbecker
2015-10-12 16:53 ` Paul E. McKenney
2015-10-12 16:55 ` Chris Metcalf
2015-10-12 17:42 ` Frederic Weisbecker
2015-10-12 17:45 ` Christoph Lameter
2015-10-12 17:50 ` Frederic Weisbecker [this message]
2015-10-12 17:52 ` Paul E. McKenney
2015-10-12 17:55 ` Frederic Weisbecker
2015-10-12 18:22 ` Paul E. McKenney
2015-10-12 18:27 ` Christoph Lameter
2015-10-12 18:03 ` Chris Metcalf
2015-10-12 19:52 ` Thomas Gleixner
2015-10-20 9:31 ` [tip:sched/core] " tip-bot for Frederic Weisbecker
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=20151012175027.GC1113@lerouge \
--to=fweisbec@gmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=cmetcalf@ezchip.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.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.