[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151012175027.GC1113@lerouge>
Date: Mon, 12 Oct 2015 19:50:29 +0200
From: Frederic Weisbecker <fweisbec@...il.com>
To: Christoph Lameter <cl@...ux.com>
Cc: Chris Metcalf <cmetcalf@...hip.com>, paulmck@...ux.vnet.ibm.com,
Ingo Molnar <mingo@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Mike Galbraith <umgwanakikbuti@...il.com>,
Dave Jones <davej@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Oleg Nesterov <oleg@...hat.com>,
Alexey Dobriyan <adobriyan@...il.com>,
Rik van Riel <riel@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] nohz: Revert "nohz: Set isolcpus when nohz_full is set"
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= ?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists