From: Mike Galbraith <efault@gmx.de>
To: Sasha Levin <sashal@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>
Cc: regressions@lists.linux.dev, stable@vger.kernel.org,
linux-rt-users@vger.kernel.org,
Lukas Beckmann <lbckmnn@mailbox.org>
Subject: Re: [REGRESSION] 6.12.y: d66792919d4f (sched/deadline: Use revised wakeup rule for dl_server) causes latencies up to 50ms with PREEMPT_RT
Date: Mon, 11 May 2026 17:30:01 +0200 [thread overview]
Message-ID: <72333205daf4663b6bd133efa9766c7cee7b22ef.camel@gmx.de> (raw)
In-Reply-To: <20260511141441.stable-reply-0001@kernel.org>
On Mon, 2026-05-11 at 10:21 -0400, Sasha Levin wrote:
>
> Mike's reply notes that his local 6.12-rt tree carrying the following
> three commits in cannot reproduce, while the same tree without them
> reproduces quickly:
>
> cccb45d7c429 ("sched/deadline: Less agressive dl_server handling")
> 4ae8d9aa9f9d ("sched/deadline: Fix dl_server getting stuck")
> a3a70caf7906 ("sched/deadline: Fix dl_server behaviour")
>
> d66792919d4f's upstream commit message explicitly says it relies on the
> state established by a3a70caf7906, and none of the three are in 6.12.y.
>
> Could you give those three commits a spin on top of 6.12.y (keeping
> d66792919d4f in place) and see whether the latency goes away?
I've meanwhile tried those three alone, and the size XXL hits my box
readily reproduces in virgin source do indeed go away.
'course there may be another shoe, so...
-Mike
next prev parent reply other threads:[~2026-05-11 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 20:57 [REGRESSION] 6.12.y: d66792919d4f (sched/deadline: Use revised wakeup rule for dl_server) causes latencies up to 50ms with PREEMPT_RT Lukas Beckmann
2026-05-11 5:50 ` Mike Galbraith
2026-05-11 14:21 ` Sasha Levin
2026-05-11 15:30 ` Mike Galbraith [this message]
2026-05-11 22:08 ` Lukas Beckmann
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=72333205daf4663b6bd133efa9766c7cee7b22ef.camel@gmx.de \
--to=efault@gmx.de \
--cc=juri.lelli@redhat.com \
--cc=lbckmnn@mailbox.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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