From: Ryan Roberts <ryan.roberts@arm.com>
To: Mel Gorman <mgorman@techsingularity.net>,
Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Madadi Vineeth Reddy <vineethr@linux.ibm.com>,
Juri Lelli <juri.lelli@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Valentin Schneider <vschneid@redhat.com>,
Chris Mason <clm@meta.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/fair: Disable scheduler feature NEXT_BUDDY
Date: Tue, 20 Jan 2026 11:45:50 +0000 [thread overview]
Message-ID: <2a52aaea-b13d-40e7-98f7-266f761dd634@arm.com> (raw)
In-Reply-To: <fyqsk63pkoxpeaclyqsm5nwtz3dyejplr7rg6p74xwemfzdzuu@7m7xhs5aqpqw>
On 20/01/2026 11:33, Mel Gorman wrote:
> NEXT_BUDDY was disabled with the introduction of EEVDF and enabled again
> after NEXT_BUDDY was rewritten for EEVDF by commit e837456fdca8 ("sched/fair:
> Reimplement NEXT_BUDDY to align with EEVDF goals"). It was not expected
> that this would be a universal win without a crystal ball instruction
> but the reported regressions are a concern [1][2] even if gains were
> also reported. Specifically;
>
> o mysql with client/server running on different servers regresses
> o specjbb reports lower peak metrics
> o daytrader regresses
>
> The mysql is realistic and a concern. It needs to be confirmed if
> specjbb is simply shifting the point where peak performance is measured
> but still a concern. daytrader is considered to be representative of a
> real workload.
>
> Access to test machines is currently problematic for verifying any fix to
> this problem. Disable NEXT_BUDDY for now by default until the root causes
> are addressed.
>
> Link: https://lore.kernel.org/lkml/4b96909a-f1ac-49eb-b814-97b8adda6229@arm.com [1]
> Link: https://lore.kernel.org/lkml/ec3ea66f-3a0d-4b5a-ab36-ce778f159b5b@linux.ibm.com [2]
> Signed-off-by: Mel Gorman <mgorman@techsingularity.net>
Thanks for posting this, Mel. And sorry I've been slow getting back to you in
the other thread. It's still on my list to respond properly and get the data
that you and Peter were requesting, but I've been spinning plates this week.
Hopefully I can get to it next week.
In the mean time I'll request a full benchmark run with this patch on top of
-rc6 to confirm our observed regressions go away (although I think we are pretty
confident they will).
Thanks,
Ryan
> ---
> kernel/sched/features.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/sched/features.h b/kernel/sched/features.h
> index 980d92bab8ab..136a6584be79 100644
> --- a/kernel/sched/features.h
> +++ b/kernel/sched/features.h
> @@ -29,7 +29,7 @@ SCHED_FEAT(PREEMPT_SHORT, true)
> * wakeup-preemption), since its likely going to consume data we
> * touched, increases cache locality.
> */
> -SCHED_FEAT(NEXT_BUDDY, true)
> +SCHED_FEAT(NEXT_BUDDY, false)
>
> /*
> * Allow completely ignoring cfs_rq->next; which can be set from various
next parent reply other threads:[~2026-01-20 11:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fyqsk63pkoxpeaclyqsm5nwtz3dyejplr7rg6p74xwemfzdzuu@7m7xhs5aqpqw>
2026-01-20 11:45 ` Ryan Roberts [this message]
2026-01-22 3:53 ` [PATCH] sched/fair: Disable scheduler feature NEXT_BUDDY Madadi Vineeth Reddy
2026-01-22 13:38 ` Ryan Roberts
2026-01-22 17:34 ` Vincent Guittot
2026-01-22 17:37 ` Vincent Guittot
2026-01-23 9:53 ` Peter Zijlstra
2026-01-23 10:04 ` Vincent Guittot
2026-01-23 10:09 ` Peter Zijlstra
2026-01-23 10:42 ` Vincent Guittot
2026-01-23 11:32 ` Ryan Roberts
2026-01-23 11:35 ` Vincent Guittot
2026-01-23 11:06 ` [tip: sched/urgent] " tip-bot2 for Mel Gorman
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=2a52aaea-b13d-40e7-98f7-266f761dd634@arm.com \
--to=ryan.roberts@arm.com \
--cc=clm@meta.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vineethr@linux.ibm.com \
--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