From: Andreas Ziegler <br025@umbiko.net>
To: Juri Lelli <juri.lelli@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: sched/deadline: Use revised wakeup rule for dl_server
Date: Mon, 11 May 2026 14:13:12 +0000 [thread overview]
Message-ID: <1ad125a7403c09166920de4e004bfc6d@umbiko.net> (raw)
In-Reply-To: <agHPu0WAv46ICYV3@jlelli-thinkpadt14gen4.remote.csb>
Hi Juri,
On 2026-05-11 12:46, Juri Lelli wrote:
> Hello,
>
> On 08/05/26 08:09, Andreas Ziegler wrote:
>> Linux kernel version: 6.12
>> CONFIG_PREEMPT_RT (w/ PREEMPT_RT patch applied)
>> Architecture: aarch64
>> Platform: Raspberry Pi 4
>>
>> Hi everyone,
>>
>> Commit d66792919d4f (sched/deadline: Use revised wakeup rule for
>> dl_server)
>> [1] introduced a marked degradation in scheduling latency for
>> real-time
>> tasks in the presence of heavy I/O load.
>
> Can this be the same regression reported here?
>
> https://marc.info/?l=linux-rt-users&m=177844667227991
Yes, this is the same issue. I wonder where the 50 ms are coming from
... The value is fairly consistent also in my results.
> Please notice the list of missing subsequent fixes Mike is suggesting
> to
> test with.
>
> https://marc.info/?l=linux-rt-users&m=177847863710263&w=2
I will take a look at the mentioned patches.
> Thanks,
> Juri
Thank you for the update,
Andreas
prev parent reply other threads:[~2026-05-11 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 8:09 sched/deadline: Use revised wakeup rule for dl_server Andreas Ziegler
2026-05-08 9:20 ` Christian Loehle
2026-05-08 12:06 ` Andreas Ziegler
2026-05-08 14:13 ` Christian Loehle
2026-05-09 11:42 ` Andreas Ziegler
2026-05-11 9:47 ` Christian Loehle
2026-05-11 12:37 ` Andreas Ziegler
2026-05-11 12:46 ` Juri Lelli
2026-05-11 14:13 ` Andreas Ziegler [this message]
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=1ad125a7403c09166920de4e004bfc6d@umbiko.net \
--to=br025@umbiko.net \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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