From: Usama Arif <usama.arif@linux.dev>
To: Usama Arif <usama.arif@linux.dev>
Cc: anna-maria@linutronix.de, frederic@kernel.org,
linux-kernel@vger.kernel.org, mingo@kernel.org, tglx@kernel.org,
hannes@cmpxchg.org, shakeel.butt@linux.dev, riel@surriel.com
Subject: Re: [PATCH v2] tick/nohz: Avoid unused timekeeping_max_deferment() calls
Date: Fri, 25 Sep 2026 02:16:43 -0700 [thread overview]
Message-ID: <20260925091645.523937-1-usama.arif@linux.dev> (raw)
In-Reply-To: <20260918133408.2834751-1-usama.arif@linux.dev>
On Fri, 18 Sep 2026 06:34:08 -0700 Usama Arif <usama.arif@linux.dev> wrote:
> tick_nohz_next_event() limits a CPU's sleep interval to the maximum
> deferment supported by the current clocksource when that CPU owns the
> do_timer() duty. If the duty is unassigned, the limit also applies when
> the CPU's TS_FLAG_DO_TIMER_LAST flag is set.
>
> After the early timer checks, the function currently reads the maximum
> deferment unconditionally. It then replaces the result with KTIME_MAX
> unless one of the two conditions above applies.
>
> timekeeping_max_deferment() performs a seqcount-protected read of the
> shared timekeeper and follows its clocksource pointer. Check the do_timer
> state first and avoid this work when the result would be discarded. This
> leaves the resulting expiry unchanged and reduces accesses to timekeeper
> data that is modified regularly.
>
> On x86-64 this removes 18-20 dynamically executed instructions, including
> the call, from the common non-owner path when the seqcount does not retry.
>
> Signed-off-by: Usama Arif <usama.arif@linux.dev>
> ---
> v1 -> v2:
> - Remove the unnecessary comment and delta variable (Frederic Weisbecker).
> ---
> kernel/time/tick-sched.c | 23 ++++++++++++-----------
> 1 file changed, 12 insertions(+), 11 deletions(-)
Hi,
Just wanted to check if there are any comments or reviews for this patch?
Thanks!
Usama
>
> diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
> index c8f2c4a503b08..a7893a079a83f 100644
> --- a/kernel/time/tick-sched.c
> +++ b/kernel/time/tick-sched.c
> @@ -816,7 +816,7 @@ u64 get_jiffies_update(unsigned long *basej)
> */
> static ktime_t tick_nohz_next_event(struct tick_sched *ts, int cpu)
> {
> - u64 basemono, next_tick, delta, expires;
> + u64 basemono, next_tick, expires;
> unsigned long basejiff;
> int tick_cpu;
>
> @@ -856,8 +856,7 @@ static ktime_t tick_nohz_next_event(struct tick_sched *ts, int cpu)
> * If the tick is due in the next period, keep it ticking or
> * force prod the timer.
> */
> - delta = next_tick - basemono;
> - if (delta <= (u64)TICK_NSEC) {
> + if (next_tick - basemono <= (u64)TICK_NSEC) {
> /*
> * We've not stopped the tick yet, and there's a timer in the
> * next period, so no point in stopping it either, bail.
> @@ -873,17 +872,19 @@ static ktime_t tick_nohz_next_event(struct tick_sched *ts, int cpu)
> * the sleep time to the timekeeping 'max_deferment' value.
> * Otherwise we can sleep as long as we want.
> */
> - delta = timekeeping_max_deferment();
> tick_cpu = READ_ONCE(tick_do_timer_cpu);
> if (tick_cpu != cpu &&
> - (tick_cpu != TICK_DO_TIMER_NONE || !tick_sched_flag_test(ts, TS_FLAG_DO_TIMER_LAST)))
> - delta = KTIME_MAX;
> -
> - /* Calculate the next expiry time */
> - if (delta < (KTIME_MAX - basemono))
> - expires = basemono + delta;
> - else
> + (tick_cpu != TICK_DO_TIMER_NONE || !tick_sched_flag_test(ts, TS_FLAG_DO_TIMER_LAST))) {
> expires = KTIME_MAX;
> + } else {
> + expires = timekeeping_max_deferment();
> +
> + /* Calculate the next expiry time */
> + if (expires < (KTIME_MAX - basemono))
> + expires += basemono;
> + else
> + expires = KTIME_MAX;
> + }
>
> ts->timer_expires = min_t(u64, expires, next_tick);
>
> --
> 2.53.0-Meta
>
>
prev parent reply other threads:[~2026-09-25 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 13:34 Usama Arif
2026-09-25 9:16 ` Usama Arif [this message]
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=20260925091645.523937-1-usama.arif@linux.dev \
--to=usama.arif@linux.dev \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=riel@surriel.com \
--cc=shakeel.butt@linux.dev \
--cc=tglx@kernel.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®