From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Hui Su <sh_def@163.com>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>
Cc: Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched/pelt: Fix truncation of the PELT period count
Date: Thu, 22 Oct 2026 14:04:27 +0530 [thread overview]
Message-ID: <aa72774f-ad04-4733-8faa-0853a32c2e4c@amd.com> (raw)
In-Reply-To: <20261022034930.225042-1-sh_def@163.com>
Hello Hui,
On 10/22/2026 9:19 AM, Hui Su wrote:
> accumulate_sum() computes the number of elapsed PELT periods in a
> u64 but returns u32. When the count is a multiple of 2^32, it is
So at least an hour between PELT updates! I suppose it is possible
with nohz so not too far fetched.
> truncated to zero even though the PELT sums have been updated.
>
> The caller interprets zero as no period boundary crossed and skips
> recomputing the averages, leaving *_avg stale relative to *_sum.
>
> Return only whether any period elapsed, which is all the caller
> needs.
>
Probably needs a:
Fixes: a481db34b9be ("sched/fair: Optimize ___update_sched_avg()") # c079629862b2
> Signed-off-by: Hui Su <sh_def@163.com>
> ---
> kernel/sched/pelt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/sched/pelt.c b/kernel/sched/pelt.c
> index 779eb58a4261..519bc9c40043 100644
> --- a/kernel/sched/pelt.c
> +++ b/kernel/sched/pelt.c
> @@ -146,7 +146,7 @@ accumulate_sum(u64 delta, struct sched_avg *sa,
> if (running)
> sa->util_sum += contrib << SCHED_CAPACITY_SHIFT;
>
> - return periods;
> + return !!periods;
I would actually favor changing return type to u64. Since
accumulate_sum() is only called in one place, and that too within an
'if' condition, I'm sure compiler can optimize it similarly.
> }
>
> /*
--
Thanks and Regards,
Prateek
next prev parent reply other threads:[~2026-10-22 8:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 3:49 Hui Su
2026-10-22 8:34 ` K Prateek Nayak [this message]
2026-10-22 8:39 ` Vincent Guittot
2026-10-22 9:37 ` Hui Su
2026-10-22 8:37 ` Vincent Guittot
2026-10-22 9:37 ` Hui Su
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=aa72774f-ad04-4733-8faa-0853a32c2e4c@amd.com \
--to=kprateek.nayak@amd.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sh_def@163.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
/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®