From: Mike Galbraith <efault@gmx.de>
To: Tom Gebhardt <tomge68@gmail.com>
Cc: peterz@infradead.org, mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: sched/fair: DELAY_DEQUEUE causes ~25% pipe IPC regression on Raspberry Pi 5
Date: Thu, 23 Apr 2026 06:51:20 +0200 [thread overview]
Message-ID: <8f02df669230c771cb34aec704e287d9ef2efa6a.camel@gmx.de> (raw)
In-Reply-To: <0a93288ace2a95616066f7a26cc45d6407dc5147.camel@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
On Tue, 2026-04-21 at 05:55 +0200, Mike Galbraith wrote:
> On Mon, 2026-04-20 at 12:59 +0200, Tom Gebhardt wrote:
>
>
> > Would you be willing to run the 6.6 comparison with stress-ng 0.15.06
> > on your Pi 5?
>
> No need, your reported DELAY_DEQUEUE impact for 6.12.75+rpt-rpi-2712
> appeared with stress-ng 0.15.06.
>
> However, my local 6.12.y branch kernel, which has all eevdf fixes as
> well as Peter's still pending sched/ttwu series, still does NOT repro.
>
> git@homer:..git/raspberrypi-kernel> quilt applied|grep delay
> patches/eevdf/WIP/0043-sched-fair-Removed-unsued-cfs_rq.h_nr_delayed.patch
> patches/eevdf/WIP/0047-sched-fair-Do-not-try-to-migrate-delayed-dequeue-task.patch <== ?
> patches/eevdf/WIP/0065-sched-Change-ttwu_runnable-vs-sched_delayed.patch
> patches/eevdf/WIP/0066-sched-Add-ttwu_queue-support-for-delayed-tasks.patch
> patches/eevdf/WIP/0089-sched-fair-Prevent-negative-lag-increase-during-delayed-dequeue.patch <== ?
I've finally finished slogging through my quilt backport battery, and
my dinky/cute rpi5 asserts that what prevents the local heavily patched
rpi-6.12-y@6.12.81 kernel from reproducing has nothing to do with
pointed at suspects, rather Peter's long pending ttwu series is
entirely responsible.
Validation enabling tarball attached.
-Mike
[-- Attachment #2: peterz-queue-ttwu.tar.gz --]
[-- Type: application/x-compressed-tar, Size: 9155 bytes --]
next prev parent reply other threads:[~2026-04-23 4:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 12:22 Tom Gebhardt
2026-04-16 20:04 ` Christian Loehle
2026-04-17 15:42 ` Vincent Guittot
2026-04-18 16:12 ` Tom Gebhardt
2026-04-20 14:27 ` Vincent Guittot
2026-04-20 3:53 ` Mike Galbraith
2026-04-20 10:59 ` Tom Gebhardt
2026-04-21 3:55 ` Mike Galbraith
2026-04-21 12:46 ` Tom Gebhardt
2026-04-21 13:14 ` Mike Galbraith
2026-04-23 4:51 ` Mike Galbraith [this message]
2026-04-23 8:04 ` 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=8f02df669230c771cb34aec704e287d9ef2efa6a.camel@gmx.de \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tomge68@gmail.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®