All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Chris Metcalf <cmetcalf@ezchip.com>
Cc: 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>, Christoph Lameter <cl@linux.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:42:41 +0200	[thread overview]
Message-ID: <20151012174238.GA1113@lerouge> (raw)
In-Reply-To: <561BE5FC.1020300@ezchip.com>

On Mon, Oct 12, 2015 at 12:55:24PM -0400, Chris Metcalf wrote:
> On 10/12/2015 12:53 PM, Paul E. McKenney wrote:
> 
> Is it worth starting to think about grouping things under the
> "task isolation" model somehow?  "task_isolation_cpus=1-31"
> or some such for this, and then that just sets up the nohz_full
> and isolcpus options under the hood?

Yeah if I could do it again, I would have rather created something like
cpu_isolation= (which name would conflict with isolcpus though) instead
of nohz_full=, because nohz_full= is really just a subset of what people
want.

But yeah if you guys want to create a new parameter that gathers nohz
and isolcpus I think we can.

task_isolation is really just about tasks so it should be another name.

  reply	other threads:[~2015-10-12 17:42 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 [this message]
2015-10-12 17:45           ` Christoph Lameter
2015-10-12 17:50             ` Frederic Weisbecker
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=20151012174238.GA1113@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.