From: Peter Zijlstra <peterz@infradead.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Doug Smythies <dsmythies@telus.net>,
K Prateek Nayak <kprateek.nayak@amd.com>,
mingo@kernel.org, juri.lelli@redhat.com,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
linux-kernel@vger.kernel.org, wangtao554@huawei.com,
quzicheng@huawei.com, wuyun.abel@bytedance.com
Subject: Re: [PATCH 0/4] sched: Various reweight_entity() fixes
Date: Wed, 11 Feb 2026 10:01:44 +0100 [thread overview]
Message-ID: <20260211090144.GY1282955@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <CAKfTPtAUhTPozVhH8U+TZFopZ_ODQ3kZKhQVoB70EJUnmY=QpQ@mail.gmail.com>
On Wed, Feb 11, 2026 at 09:49:57AM +0100, Vincent Guittot wrote:
> On Wed, 11 Feb 2026 at 06:21, Doug Smythies <dsmythies@telus.net> wrote:
> >
> > On 2026.02.10 12:52 Vincent Guittot wrote:
> > > On Mon, 9 Feb 2026 at 16:47, Peter Zijlstra <peterz@infradead.org> wrote:
> > >> On Wed, Feb 04, 2026 at 03:45:58PM +0530, K Prateek Nayak wrote:
> > >
> > ... delete ...
> >
> > > This patch w/ the patchset on top of tip/sched/core create regressions
> > > for hackbench (tbench doesn't seem to be impacted) on my dragonboard
> > > rb5
> > > All hackbench tests are regressing. Some results below
> > ...
> > > hackbench 8 group process socket
> > > 0.650(+/-1%) vs 2.361(+/-8.8%) : -263%
> > ...
> >
> > Very interesting.
> > I only know of the Phoronix version of hackbench.
> > I ran what I believe to be a similar scenario to yours:
> > 10 test runs each (the default is 3):
> >
> > Kernel 6.19-rc8: 23.228 seconds average, deviation 0.39%
> > Kernel 6.19-rc8-pz-v2: 85.755 seconds average, deviation 3.33%
> > 269% regression. (very similar to Vicent's results)
>
> patch 3 + a default value for sum_shift restore the performance
> cfs_rq->sum_shift = SCHED_FIXEDPOINT_SHIFT;
Hurmph.. I really wanted to do away with that, because those small
weights are fairly common in the cgroup shares thing, and will be more
common still if we do a flat pick.
> There 2 issues with patch 3
>
> *one scale_load_down remains in avg_vruntime
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 25c398ff0d59..3143ae7f07b0 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -778,7 +778,7 @@ u64 avg_vruntime(struct cfs_rq *cfs_rq)
>
> if (weight) {
> if (curr) {
> - unsigned long w = scale_load_down(curr->load.weight);
> + unsigned long w =
> avg_vruntime_weight(curr->load.weight);
>
> runtime += entity_key(cfs_rq, curr) * w;
> weight += w;
AAARGHHH!! Sorry about that, clearly I've not been careful with
reshuffling patches :-(
> and we still use calc_delta_fair() in update_entity_lag() but
> calc_delta_fair() use scale_load_down()
Hmmm, indeed, let me see if I can do something about that. Perhaps just
eat the 64bit division on 64bit systems.
Anyway, let me go poke at all this.
next prev parent reply other threads:[~2026-02-11 9:01 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 9:34 Peter Zijlstra
2026-01-30 9:34 ` [PATCH 1/4] sched/fair: Only set slice protection at pick time Peter Zijlstra
2026-01-30 15:52 ` Vincent Guittot
2026-01-30 9:34 ` [PATCH 2/4] sched/eevdf: Update se->vprot in reweight_entity() Peter Zijlstra
2026-01-30 16:20 ` Vincent Guittot
2026-01-30 9:34 ` [PATCH 3/4] sched/fair: Increase weight bits for avg_vruntime Peter Zijlstra
2026-01-30 9:34 ` [PATCH 4/4] sched/fair: Revert 6d71a9c61604 ("sched/fair: Fix EEVDF entity placement bug causing scheduling lag") Peter Zijlstra
2026-01-31 1:47 ` Zhang Qiao
2026-01-31 15:21 ` Peter Zijlstra
2026-02-02 9:12 ` Peter Zijlstra
2026-02-02 9:24 ` Peter Zijlstra
2026-02-02 11:23 ` Zhang Qiao
2026-02-01 17:13 ` [PATCH 0/4] sched: Various reweight_entity() fixes Doug Smythies
2026-02-03 6:45 ` K Prateek Nayak
2026-02-03 11:11 ` Peter Zijlstra
2026-02-03 12:19 ` K Prateek Nayak
2026-02-03 16:36 ` Doug Smythies
2026-02-10 18:13 ` Peter Zijlstra
2026-02-11 5:51 ` Doug Smythies
2026-02-04 10:15 ` K Prateek Nayak
2026-02-09 15:47 ` Peter Zijlstra
2026-02-09 16:52 ` K Prateek Nayak
2026-02-10 5:16 ` K Prateek Nayak
2026-02-10 10:29 ` Peter Zijlstra
2026-02-10 15:41 ` Doug Smythies
2026-02-10 18:09 ` K Prateek Nayak
2026-02-10 18:35 ` Peter Zijlstra
2026-02-10 20:04 ` K Prateek Nayak
2026-02-11 6:28 ` K Prateek Nayak
2026-02-11 8:50 ` K Prateek Nayak
2026-02-11 23:09 ` Doug Smythies
2026-02-10 18:52 ` Peter Zijlstra
2026-02-10 20:52 ` Vincent Guittot
2026-02-11 5:21 ` Doug Smythies
2026-02-11 8:49 ` Vincent Guittot
2026-02-11 9:01 ` Peter Zijlstra [this message]
2026-02-11 10:48 ` Peter Zijlstra
2026-02-11 10:49 ` Peter Zijlstra
2026-02-11 11:15 ` Vincent Guittot
2026-02-11 16:28 ` Peter Zijlstra
2026-02-12 7:43 ` K Prateek Nayak
2026-02-12 11:59 ` Peter Zijlstra
2026-02-12 17:16 ` Peter Zijlstra
2026-02-12 17:24 ` Vincent Guittot
2026-02-12 19:31 ` Peter Zijlstra
2026-02-13 5:22 ` K Prateek Nayak
2026-02-13 6:44 ` Peter Zijlstra
2026-02-13 10:50 ` Peter Zijlstra
2026-02-13 14:29 ` K Prateek Nayak
2026-02-14 6:31 ` Doug Smythies
2026-02-21 22:51 ` Doug Smythies
2026-02-12 19:29 ` Peter Zijlstra
2026-02-12 19:37 ` Doug Smythies
2026-02-13 6:04 ` K Prateek Nayak
2026-02-11 16:21 ` Peter Zijlstra
2026-02-12 5:54 ` Doug Smythies
2026-02-12 7:51 ` Peter Zijlstra
2026-02-12 15:47 ` Doug Smythies
2026-02-12 7:46 ` Peter Zijlstra
2026-02-11 23:25 ` Doug Smythies
2026-02-11 8:48 ` Peter Zijlstra
2026-02-04 10:44 ` Peter Zijlstra
2026-02-14 7:20 ` Shubhang Kaushik
2026-02-16 3:14 ` K Prateek Nayak
2026-02-16 10:59 ` Dietmar Eggemann
2026-02-17 14:37 ` Dietmar Eggemann
2026-02-17 22:02 ` Shubhang Kaushik
2026-02-17 4:20 ` K Prateek Nayak
2026-02-18 18:37 ` Shubhang Kaushik
2026-02-19 7:53 ` 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=20260211090144.GY1282955@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=dsmythies@telus.net \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=quzicheng@huawei.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=wangtao554@huawei.com \
--cc=wuyun.abel@bytedance.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®