public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Rik van Riel <riel@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Chris Metcalf <cmetcalf@mellanox.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Luiz Capitulino <lcapitulino@redhat.com>,
	Christoph Lameter <cl@linux.com>,
	"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>,
	Ingo Molnar <mingo@kernel.org>, Mike Galbraith <efault@gmx.de>,
	Wanpeng Li <kernellwp@gmail.com>
Subject: Re: [RFC PATCH 01/12] housekeeping: Move housekeeping related code to its own file
Date: Fri, 1 Sep 2017 00:58:18 +0200	[thread overview]
Message-ID: <20170831225816.GA18249@lerouge> (raw)
In-Reply-To: <1504210576.12821.6.camel@redhat.com>

On Thu, Aug 31, 2017 at 04:16:16PM -0400, Rik van Riel wrote:
> On Wed, 2017-08-23 at 03:51 +0200, Frederic Weisbecker wrote:
> > The housekeeping code is currently tied to the nohz code. As we are
> > planning to make housekeeping independant from it, start with moving
> > the relevant code to its own file.
> > 
> Why are nohz full and housekeeping being
> decoupled from each other?
> 
> Won't people want to use them together?
> 
> What use case am I missing?

So nohz is really just a feature and it shouldn't decide about other isolation
features. It should be the opposite: isolation picks up nohz, alongside other
isolation things. I think we did a layering misdesign. So it's mostly just a code
reorganisation.

While at it, isolcpus= is also part of the isolation toolset. So I thought we should
centralize all this isolation code in a common subsystem.

  reply	other threads:[~2017-08-31 22:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23  1:50 [RFC 00/12] Introduce housekeeping subsystem v2 Frederic Weisbecker
2017-08-23  1:51 ` [RFC PATCH 01/12] housekeeping: Move housekeeping related code to its own file Frederic Weisbecker
2017-08-31 20:16   ` Rik van Riel
2017-08-31 22:58     ` Frederic Weisbecker [this message]
2017-08-23  1:51 ` [RFC PATCH 02/12] watchdog: Use housekeeping_cpumask() instead of ad-hoc version Frederic Weisbecker
2017-08-23  1:51 ` [RFC PATCH 03/12] housekeeping: Provide a dynamic off-case to housekeeping_any_cpu() Frederic Weisbecker
2017-08-23  1:51 ` [RFC PATCH 04/12] housekeeping: Make housekeeping cpumask private Frederic Weisbecker
2017-08-23  1:51 ` [RFC PATCH 05/12] housekeeping: Use its own static key Frederic Weisbecker
2017-08-23  1:51 ` [RFC PATCH 06/12] housekeeping: Rename is_housekeeping_cpu to housekeeping_cpu Frederic Weisbecker
2017-08-23  1:51 ` [RFC PATCH 07/12] housekeeping: Move it under own config, independant from NO_HZ Frederic Weisbecker
2017-08-23  1:51 ` [RFC PATCH 08/12] housekeeping: Introduce housekeeping flags Frederic Weisbecker
2017-08-23  1:51 ` [RFC PATCH 09/12] workqueue: Affine unbound workqueues to housekeeping cpumask Frederic Weisbecker
2017-08-23  1:51 ` [RFC PATCH 10/12] housekeeping: Affine unbound kthreads Frederic Weisbecker
2017-08-23  1:51 ` [RFC PATCH 11/12] housekeeping: Handle nohz_full= parameter Frederic Weisbecker
2017-08-23  1:51 ` [RFC PATCH 12/12] housekeeping: Reimplement isolcpus on housekeeping Frederic Weisbecker
2017-08-23 14:55   ` Christopher Lameter
2017-08-24 13:19     ` Frederic Weisbecker
2017-08-28 10:10     ` Peter Zijlstra
2017-08-28 15:38       ` Christopher Lameter
2017-08-28 10:09   ` Peter Zijlstra
2017-08-28 13:23     ` Frederic Weisbecker
2017-08-28 13:31       ` Peter Zijlstra
2017-08-28 15:27         ` Frederic Weisbecker
2017-08-28 16:24           ` Peter Zijlstra
2017-08-28 16:53             ` Christopher Lameter
2017-08-28 17:33             ` Frederic Weisbecker
2017-08-31 18:53               ` Thomas Gleixner
2017-08-31 23:00                 ` 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=20170831225816.GA18249@lerouge \
    --to=fweisbec@gmail.com \
    --cc=cl@linux.com \
    --cc=cmetcalf@mellanox.com \
    --cc=efault@gmx.de \
    --cc=kernellwp@gmail.com \
    --cc=lcapitulino@redhat.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