All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Chris Metcalf <cmetcalf@mellanox.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Christoph Lameter <cl@linux.com>,
	"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>,
	Wanpeng Li <kernellwp@gmail.com>, Mike Galbraith <efault@gmx.de>,
	Rik van Riel <riel@redhat.com>
Subject: Re: [GIT PULL] isolation: 1Hz residual tick offloading v3
Date: Fri, 12 Jan 2018 14:18:13 -0500	[thread overview]
Message-ID: <20180112141813.32dcc84d@redhat.com> (raw)
In-Reply-To: <1515039937-367-1-git-send-email-frederic@kernel.org>

On Thu,  4 Jan 2018 05:25:32 +0100
Frederic Weisbecker <frederic@kernel.org> wrote:

> Ingo,
> 
> Please pull the sched/0hz branch that can be found at:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> 	sched/0hz
> 
> HEAD: 9e932b2cc707209febd130978a5eb9f4a943a3f4
> 
> --
> Now that scheduler_tick() has become resilient towards the absence of
> ticks, current->sched_class->task_tick() is the last piece that needs
> at least 1Hz tick to keep scheduler stats alive.
> 
> This patchset adds a flag to the isolcpus boot option to offload the
> residual 1Hz tick. This way the nohz_full CPUs don't have anymore tick
> (assuming nothing else requires it) as their residual 1Hz tick is
> offloaded to the housekeepers.
> 
> For quick testing, say on CPUs 1-7:
> 
> 	"isolcpus=nohz_offload,domain,1-7"

Sorry for being very late to this series, but I've a few comments to
make (one right now and others in individual patches).

Why are extending isolcpus= given that it's a deprecated interface?
Some people have already moved away from isolcpus= now, but with this
new feature they will be forced back to using it.

What about just adding the new functionality to nohz_full=? That is,
no new options, just make the tick go away since this has always been
what nohz_full= was intended to do?

> 
> Thanks,
> 	Frederic
> ---
> 
> Frederic Weisbecker (5):
>       sched: Rename init_rq_hrtick to hrtick_rq_init
>       sched/isolation: Add scheduler tick offloading interface
>       nohz: Allow to check if remote CPU tick is stopped
>       sched/isolation: Residual 1Hz scheduler tick offload
>       sched/isolation: Document "nohz_offload" flag
> 
> 
>  Documentation/admin-guide/kernel-parameters.txt |  7 +-
>  include/linux/sched/isolation.h                 |  3 +-
>  include/linux/tick.h                            |  2 +
>  kernel/sched/core.c                             | 94 +++++++++++++++++++++++--
>  kernel/sched/isolation.c                        | 10 +++
>  kernel/sched/sched.h                            |  2 +
>  kernel/time/tick-sched.c                        |  7 ++
>  7 files changed, 117 insertions(+), 8 deletions(-)
> 

  parent reply	other threads:[~2018-01-12 19:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04  4:25 [GIT PULL] isolation: 1Hz residual tick offloading v3 Frederic Weisbecker
2018-01-04  4:25 ` [PATCH 1/5] sched: Rename init_rq_hrtick to hrtick_rq_init Frederic Weisbecker
2018-01-04  4:25 ` [PATCH 2/5] sched/isolation: Add scheduler tick offloading interface Frederic Weisbecker
2018-01-04  4:25 ` [PATCH 3/5] nohz: Allow to check if remote CPU tick is stopped Frederic Weisbecker
2018-01-04  4:25 ` [PATCH 4/5] sched/isolation: Residual 1Hz scheduler tick offload Frederic Weisbecker
2018-01-12 19:22   ` Luiz Capitulino
2018-01-16 15:57     ` Frederic Weisbecker
2018-01-16 16:53       ` Luiz Capitulino
2018-01-04  4:25 ` [PATCH 5/5] sched/isolation: Document "nohz_offload" flag Frederic Weisbecker
2018-01-12 19:18 ` Luiz Capitulino [this message]
2018-01-16 15:41   ` [GIT PULL] isolation: 1Hz residual tick offloading v3 Frederic Weisbecker
2018-01-16 16:52     ` Luiz Capitulino
2018-01-16 22:51       ` Frederic Weisbecker
2018-01-17 17:38         ` Luiz Capitulino
2018-01-18  3:04           ` Frederic Weisbecker
2018-01-18 14:02             ` Luiz Capitulino
2018-01-16 17:58     ` Mike Galbraith
2018-01-16 22:53       ` Frederic Weisbecker
2018-01-17 14:51       ` Christopher Lameter
2018-01-17 15:59         ` Mike Galbraith
2018-01-17 16:32           ` Christopher Lameter
2018-01-17 16:58             ` Mike Galbraith

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=20180112141813.32dcc84d@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=cl@linux.com \
    --cc=cmetcalf@mellanox.com \
    --cc=efault@gmx.de \
    --cc=frederic@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.