From: Mike Galbraith <efault@gmx.de>
To: Aishwarya Rambhadran <aishwarya.rambhadran@arm.com>,
Chen Yu <yu.c.chen@intel.com>,
kprateek.nayak@amd.com
Cc: Peter Zijlstra <peterz@infradead.org>,
mingo@kernel.org, longman@redhat.com,
chenridong@huaweicloud.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
vschneid@redhat.com, tj@kernel.org, hannes@cmpxchg.org,
mkoutny@suse.com, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org, jstultz@google.com,
qyousef@layalina.io, Ryan Roberts <ryan.roberts@arm.com>,
chen.yu@linux.dev
Subject: Re: [REGRESSION] [PATCH v3 7/7] sched/eevdf: Move to a single runqueue
Date: Mon, 12 Oct 2026 13:27:58 +0200 [thread overview]
Message-ID: <eac663e09be5dbadaded334f2f80d2c21f3b14cb.camel@gmx.de> (raw)
In-Reply-To: <d9f31316-38fb-4841-9050-8a9f3a042847@arm.com>
On Wed, 2026-10-07 at 17:35 +0530, Aishwarya Rambhadran wrote:
> Hi all,
>
> Thanks for the suggestions. I ran a couple of follow-up tests on the
> same AWS Graviton3 (m7g.metal) setup with v7.3-rc4:
>
> 1. Disable WA_WEIGHT:
> echo NO_WA_WEIGHT > /sys/kernel/debug/sched/features
>
> 2. Use the "smp" cgroup mode:
> echo smp > /sys/kernel/debug/sched/cgroup_mode
>
> Both tests were run with 20 repeats across 2 boot sessions. Below are
> the request latency p99 results for schbench configurations discussed
> earlier (usec, smaller is better):
>
> message-thread:16, worker-thread:16
> v7.2 = 662869
> v7.3-rc4 = 969557
> NO_WA_WEIGHT = 958541
> smp = 723098
>
> message-thread:64, worker-thread:4
> v7.2 = 730453
> v7.3-rc4 = 942251
> NO_WA_WEIGHT = 740454
> smp = 818483
>
> message-thread:32, worker-thread:4
> v7.2 = 74251
> v7.3-rc4 = 56725
> NO_WA_WEIGHT = 59008
> smp = 82053
>
> For the m:16 t:16 case that I originally bisected, disabling WA_WEIGHT
> does not materially change the regression. Switching to cgroup_mode=smp,
> however, recovers most of it.
I took flat back to 7.2 (to test only that) and did a little mixed load
7.2-virgin vs 7.2+flat testing with defaults. CPU distribution delta
when switching competitor load configuration from 1 group of 8 to 4
groups of 2 vs a fixed 4 client netperf load made it clear that numbers
for anything cgroup vs cgroup will definitely wiggle more than usual.
-Mike
next prev parent reply other threads:[~2026-10-12 11:28 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 12:40 [PATCH v3 0/7] sched: Flatten the pick Peter Zijlstra
2026-06-05 12:40 ` [PATCH v3 1/7] sched/fair: Add cgroup_mode switch Peter Zijlstra
2026-06-30 9:03 ` [tip: sched/core] " tip-bot2 for Peter Zijlstra
2026-06-05 12:40 ` [PATCH v3 2/7] sched/fair: Add cgroup_mode: up Peter Zijlstra
2026-06-05 15:07 ` Peter Zijlstra
2026-06-30 9:03 ` [tip: sched/core] " tip-bot2 for Peter Zijlstra
2026-06-05 12:40 ` [PATCH v3 3/7] sched/fair: Add cgroup_mode: max Peter Zijlstra
2026-06-10 15:09 ` Waiman Long
2026-06-10 15:42 ` Waiman Long
2026-06-11 13:49 ` Peter Zijlstra
2026-06-11 13:47 ` Peter Zijlstra
2026-06-11 20:57 ` Waiman Long
2026-06-30 9:03 ` [tip: sched/core] " tip-bot2 for Peter Zijlstra
2026-06-05 12:40 ` [PATCH v3 4/7] sched/fair: Add cgroup_mode: concur Peter Zijlstra
2026-06-30 9:03 ` [tip: sched/core] " tip-bot2 for Peter Zijlstra
2026-06-05 12:40 ` [PATCH v3 5/7] sched/fair: Add cgroup_mode: tasks Peter Zijlstra
2026-06-30 9:03 ` [tip: sched/core] " tip-bot2 for Peter Zijlstra
2026-06-05 12:40 ` [PATCH v3 6/7] sched/fair: Change the default cgroup_mode to concur Peter Zijlstra
2026-06-30 9:03 ` [tip: sched/core] " tip-bot2 for Peter Zijlstra
2026-06-05 12:40 ` [PATCH v3 7/7] sched/eevdf: Move to a single runqueue Peter Zijlstra
2026-06-20 3:54 ` Chen, Yu C
2026-06-26 11:40 ` Peter Zijlstra
2026-06-29 14:02 ` Vincent Guittot
2026-06-30 9:03 ` [tip: sched/core] sched/fair: Fix overflow in update_tg_cfs_runnable() tip-bot2 for Chen, Yu C
2026-06-30 9:03 ` [tip: sched/core] sched/eevdf: Move to a single runqueue tip-bot2 for Peter Zijlstra (Intel)
2026-09-23 14:21 ` [REGRESSION] [PATCH v3 7/7] " Aishwarya Rambhadran
2026-09-23 16:48 ` Chen Yu
2026-09-24 7:05 ` K Prateek Nayak
2026-09-24 8:19 ` Mike Galbraith
2026-09-28 3:12 ` Chen Yu
2026-09-28 13:00 ` Mike Galbraith
2026-10-07 12:05 ` Aishwarya Rambhadran
2026-10-12 11:27 ` Mike Galbraith [this message]
2026-06-09 5:37 ` [PATCH v3 0/7] sched: Flatten the pick K Prateek Nayak
2026-06-12 2:29 ` Shubhang Kaushik
2026-08-17 16:05 ` Szabina Korbai
2026-08-17 16:35 ` K Prateek Nayak
2026-08-18 9:04 ` Szabina Korbai
2026-08-18 9:16 ` Peter Zijlstra
2026-08-21 10:37 ` Szabina Korbai
2026-08-24 14:51 ` Chen Yu
2026-08-24 13: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=eac663e09be5dbadaded334f2f80d2c21f3b14cb.camel@gmx.de \
--to=efault@gmx.de \
--cc=aishwarya.rambhadran@arm.com \
--cc=bsegall@google.com \
--cc=cgroups@vger.kernel.org \
--cc=chen.yu@linux.dev \
--cc=chenridong@huaweicloud.com \
--cc=dietmar.eggemann@arm.com \
--cc=hannes@cmpxchg.org \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=mkoutny@suse.com \
--cc=peterz@infradead.org \
--cc=qyousef@layalina.io \
--cc=rostedt@goodmis.org \
--cc=ryan.roberts@arm.com \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=yu.c.chen@intel.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®