public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>,
	Chris Metcalf <cmetcalf@mellanox.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Christoph Lameter <cl@linux.com>,
	"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>,
	Ingo Molnar <mingo@kernel.org>, Rik van Riel <riel@redhat.com>,
	Wanpeng Li <kernellwp@gmail.com>
Subject: Re: [RFC PATCH 0/9] Introduce housekeeping subsystem
Date: Fri, 11 Aug 2017 15:22:37 -0400	[thread overview]
Message-ID: <20170811152237.62941895@redhat.com> (raw)
In-Reply-To: <20170811150129.GB25912@lerouge>

On Fri, 11 Aug 2017 17:01:30 +0200
Frederic Weisbecker <fweisbec@gmail.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?

  reply	other threads:[~2017-08-11 19:22 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21 13:21 [RFC PATCH 0/9] Introduce housekeeping subsystem Frederic Weisbecker
2017-07-21 13:21 ` [RFC PATCH 1/9] housekeeping: Move housekeeping related code to its own file Frederic Weisbecker
2017-07-21 13:21 ` [RFC PATCH 2/9] watchdog: Use housekeeping_cpumask() instead of ad-hoc version Frederic Weisbecker
2017-07-21 13:21 ` [RFC PATCH 3/9] housekeeping: Provide a dynamic off-case to housekeeping_any_cpu() Frederic Weisbecker
2017-07-21 13:21 ` [RFC PATCH 4/9] housekeeping: Make housekeeping cpumask private Frederic Weisbecker
2017-07-21 13:21 ` [RFC PATCH 5/9] housekeeping: Use its own static key Frederic Weisbecker
2017-07-21 13:21 ` [RFC PATCH 6/9] housekeeping: Rename is_housekeeping_cpu to housekeeping_cpu Frederic Weisbecker
2017-07-21 13:21 ` [RFC PATCH 7/9] housekeeping: Use own boot option, independant from nohz Frederic Weisbecker
2017-08-11 19:09   ` Luiz Capitulino
2017-08-12 14:10     ` Frederic Weisbecker
2017-08-13 15:13       ` Luiz Capitulino
2017-08-14 17:01         ` Frederic Weisbecker
2017-08-14 17:34           ` Luiz Capitulino
2017-08-14 18:29             ` Mike Galbraith
2017-08-15 13:07               ` Frederic Weisbecker
2017-08-15 15:15                 ` Mike Galbraith
2017-08-15 15:30                   ` Paul E. McKenney
2017-08-15 15:52                     ` Christopher Lameter
2017-08-15 15:57                       ` Mike Galbraith
2017-08-15 16:26                         ` Christopher Lameter
2017-08-16 18:00                           ` Mike Galbraith
2017-08-15 15:53                     ` Mike Galbraith
2017-07-21 13:21 ` [RFC PATCH 8/9] housekeeping: Move it under own config, independant from NO_HZ Frederic Weisbecker
2017-07-21 13:21 ` [RFC PATCH 9/9] workqueue: Affine unbound workqueues to housekeeping cpumask Frederic Weisbecker
2017-07-21 19:48 ` [RFC PATCH 0/9] Introduce housekeeping subsystem Chris Metcalf
2017-08-10 12:54   ` Frederic Weisbecker
2017-08-10 13:57     ` Chris Metcalf
2017-08-11  6:36       ` Mike Galbraith
2017-08-11 15:01         ` Frederic Weisbecker
2017-08-11 19:22           ` Luiz Capitulino [this message]
2017-08-11 15:08         ` Chris Metcalf
2017-08-11 15:35           ` Christopher Lameter
2017-08-11 15:50             ` Chris Metcalf

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=20170811152237.62941895@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=cl@linux.com \
    --cc=cmetcalf@mellanox.com \
    --cc=efault@gmx.de \
    --cc=fweisbec@gmail.com \
    --cc=kernellwp@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    --cc=tglx@linutronix.de \
    /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