mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Qais Yousef <qyousef@layalina.io>
To: Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Vincent Guittot <vincent.guittot@linaro.org>
Cc: Juri Lelli <juri.lelli@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	John Stultz <jstultz@google.com>,
	Thomas Gleixner <tglx@kernel.org>,
	Frederic Weisbecker <frederic@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] sched/tick: Decouple sched_tick() from HZ
Date: Sun, 17 May 2026 05:19:50 +0100	[thread overview]
Message-ID: <20260517041950.tqr27nax6e237roc@airbuntu> (raw)
In-Reply-To: <20260517040740.444729-1-qyousef@layalina.io>

On 05/17/26 05:07, Qais Yousef wrote:
> Previous attempt to make HZ 1000 the default [1] to help with scheduler
> responsiveness didn't get merged. But maybe for the best, as I think this idea
> of decoupling sched_tick() from HZ makes more sense. We shouldn't need to make
> a choice between how often timers should trigger vs how often should the
> scheduler update its stats/take decisions.
> 
> With HRTICK now is default on, preemption checks are less of problem. But tasks
> could need to migrate (specifically on HMP systems) and frequencies could need
> updating for solo long running tasks.
> 
> The conversion is half complete. We need to invent a new jiffy (piffy?) and
> move existing load balancing logic (and potentially other users if they want
> to) to speed them up. BUT, with push load balancer patches circulating around,
> I am not sure it is worth while or desired to speed it since we have a better
> faster mechanism to keep the system balanced without the need for the 'heavy
> handed' full load balance to trigger. The push lb can benefit from this ptick
> too to ensure more responsiveness.

Err, this whole series is RFC. Forgot to add the tag, sorry.

> 
> [1] https://lore.kernel.org/lkml/20250226000810.459547-1-qyousef@layalina.io/
> 
> Qais Yousef (3):
>   sched/tick: Decouple sched_tick() from HZ
>   sched/tick: Move TICK_NSEC users to PTICK_NSEC
>   sched/tick: Turn on PTICK by default
> 
>  kernel/sched/clock.c             |  4 +-
>  kernel/sched/core.c              | 78 +++++++++++++++++++++++++++++---
>  kernel/sched/cpufreq_schedutil.c |  2 +-
>  kernel/sched/fair.c              |  6 +--
>  kernel/sched/features.h          |  8 ++++
>  kernel/sched/sched.h             |  7 +++
>  6 files changed, 93 insertions(+), 12 deletions(-)
> 
> -- 
> 2.34.1
> 

  parent reply	other threads:[~2026-05-17  4:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-17  4:07 Qais Yousef
2026-05-17  4:07 ` [PATCH 1/3] " Qais Yousef
2026-05-17  4:07 ` [PATCH 2/3] sched/tick: Move TICK_NSEC users to PTICK_NSEC Qais Yousef
2026-05-17  4:07 ` [PATCH 3/3] sched/tick: Turn on PTICK by default Qais Yousef
2026-05-17  4:19 ` Qais Yousef [this message]
2026-05-17 14:10 ` [PATCH 0/3] sched/tick: Decouple sched_tick() from HZ David Laight
2026-05-17 15:44   ` Qais Yousef
2026-05-17 16:09     ` David Laight
2026-05-17 17:26       ` Qais Yousef
2026-05-18  7:40 ` Peter Zijlstra
2026-05-19  0:42   ` Qais Yousef
2026-05-19  9:13     ` Peter Zijlstra

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=20260517041950.tqr27nax6e237roc@airbuntu \
    --to=qyousef@layalina.io \
    --cc=frederic@kernel.org \
    --cc=jstultz@google.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@kernel.org \
    --cc=vincent.guittot@linaro.org \
    /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

all inboxes | Powered by JetHome®