[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170811152237.62941895@redhat.com>
Date: Fri, 11 Aug 2017 15:22:37 -0400
From: Luiz Capitulino <lcapitulino@...hat.com>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: Mike Galbraith <efault@....de>,
Chris Metcalf <cmetcalf@...lanox.com>,
LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Christoph Lameter <cl@...ux.com>,
"Paul E . McKenney" <paulmck@...ux.vnet.ibm.com>,
Ingo Molnar <mingo@...nel.org>, Rik van Riel <riel@...hat.com>,
Wanpeng Li <kernellwp@...il.com>
Subject: Re: [RFC PATCH 0/9] Introduce housekeeping subsystem
On Fri, 11 Aug 2017 17:01:30 +0200
Frederic Weisbecker <fweisbec@...il.com> wrote:
> > Personally, I think NOHZ_FULL_ALL should just die.
>
> Yeah, although it's still useful for automatic boot testing to detect issues
> with nohz_full on.
Maybe we could rename/modify it to be a boot-time testing option for
nohz_full?
I think we may want to simplify config and kernel command-line options.
I don't think it's a good idea to break down every single isolation
feature into a kernel command-line option. What we want in the end is
having the ability to remove all the noise from a CPU right? Why not
have a single option for that?
Powered by blists - more mailing lists