mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	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>,
	Rik van Riel <riel@redhat.com>, Wanpeng Li <kernellwp@gmail.com>
Subject: [PATCH 00/12] Introduce housekeeping subsystem v3
Date: Fri,  1 Sep 2017 18:41:35 +0200	[thread overview]
Message-ID: <1504284108-6157-1-git-send-email-fweisbec@gmail.com> (raw)

So this time I didn't change the implementation of isolcpus which relies
on NULL domains, I only pulled it to the housekeeping subsystem.

Summary of changes from v2:

* "isolcpus=" takes flags, which allows us to control nohz through it.
  For example:
	isolcpus=nohz,1-7			-- enable nohz_full to CPUs 1 to 7
	isolcpus=nohz,domain,1-7	-- enable nohz_full and isolate CPUs 1 to 7

  If no flags are passed, the default flag is "domain", so the kernel
  parameter is backward compatible.

  More flags should be added in the future to isolate a CPU from more
  details. We just need to debate how finegrained we want that.

  We also want to make sure that what is passed to isolcpus is later
  modifiable through cpusets.

* Remove workqueue and kthread isolation, we'll think about those later
  once we have an interface for them in the isolcpus flags.

git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
	core/isolation-v3

HEAD: f1292ff748c3f5cdff0c29a3a43b2231ac5005cf

Thanks,
	Frederic
---

Frederic Weisbecker (12):
      housekeeping: Move housekeeping related code to its own file
      watchdog: Use housekeeping_cpumask() instead of ad-hoc version
      housekeeping: Provide a dynamic off-case to housekeeping_any_cpu()
      housekeeping: Make housekeeping cpumask private
      housekeeping: Use its own static key
      housekeeping: Rename is_housekeeping_cpu to housekeeping_cpu
      housekeeping: Move it under own config, independant from NO_HZ
      housekeeping: Introduce housekeeping flags
      housekeeping: Handle nohz_full= parameter
      housekeeping: Move isolcpus to housekeeping
      housekeeping: Add basic isolcpus flags
      housekeeping: Document isolcpus flags


 Documentation/admin-guide/kernel-parameters.txt |  33 +++---
 drivers/base/cpu.c                              |  11 +-
 drivers/net/ethernet/tile/tilegx.c              |   6 +-
 include/linux/housekeeping.h                    |  51 ++++++++
 include/linux/sched.h                           |   2 -
 include/linux/tick.h                            |  38 +-----
 init/Kconfig                                    |   7 ++
 init/main.c                                     |   2 +
 kernel/Makefile                                 |   1 +
 kernel/cgroup/cpuset.c                          |  14 +--
 kernel/housekeeping.c                           | 148 ++++++++++++++++++++++++
 kernel/rcu/tree_plugin.h                        |   3 +-
 kernel/rcu/update.c                             |   3 +-
 kernel/sched/core.c                             |  25 +---
 kernel/sched/fair.c                             |   3 +-
 kernel/sched/topology.c                         |  21 +---
 kernel/time/tick-sched.c                        |  31 +----
 kernel/watchdog.c                               |  13 +--
 18 files changed, 272 insertions(+), 140 deletions(-)

             reply	other threads:[~2017-09-01 16:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01 16:41 Frederic Weisbecker [this message]
2017-09-01 16:41 ` [PATCH 01/12] housekeeping: Move housekeeping related code to its own file Frederic Weisbecker
2017-09-01 16:41 ` [PATCH 02/12] watchdog: Use housekeeping_cpumask() instead of ad-hoc version Frederic Weisbecker
2017-09-01 16:41 ` [PATCH 03/12] housekeeping: Provide a dynamic off-case to housekeeping_any_cpu() Frederic Weisbecker
2017-09-01 16:41 ` [PATCH 04/12] housekeeping: Make housekeeping cpumask private Frederic Weisbecker
2017-09-01 16:41 ` [PATCH 05/12] housekeeping: Use its own static key Frederic Weisbecker
2017-09-01 16:41 ` [PATCH 06/12] housekeeping: Rename is_housekeeping_cpu to housekeeping_cpu Frederic Weisbecker
2017-09-01 16:41 ` [PATCH 07/12] housekeeping: Move it under own config, independant from NO_HZ Frederic Weisbecker
2017-09-01 16:41 ` [PATCH 08/12] housekeeping: Introduce housekeeping flags Frederic Weisbecker
2017-09-01 16:41 ` [PATCH 09/12] housekeeping: Handle nohz_full= parameter Frederic Weisbecker
2017-09-01 16:41 ` [PATCH 10/12] housekeeping: Move isolcpus to housekeeping Frederic Weisbecker
2017-09-01 16:41 ` [PATCH 11/12] housekeeping: Add basic isolcpus flags Frederic Weisbecker
2017-09-01 16:41 ` [PATCH 12/12] housekeeping: Document " 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=1504284108-6157-1-git-send-email-fweisbec@gmail.com \
    --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

Powered by JetHome