From: Juri Lelli <juri.lelli@redhat.com>
To: Gabriele Monaco <gmonaco@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, jstultz@google.com,
arighi@nvidia.com, soolaugust@gmail.com, suzhidao@xiaomi.com
Subject: Re: [PATCH] sched/deadline: Use revised wakeup rule only for running dl_server
Date: Mon, 25 May 2026 08:19:42 +0200 [thread overview]
Message-ID: <ahPp_pRBb3kGuwpZ@jlelli-thinkpadt14gen4.remote.csb> (raw)
In-Reply-To: <20260522125833.264145-1-gmonaco@redhat.com>
Hi!
On 22/05/26 14:58, Gabriele Monaco wrote:
> Commit 14a857056466 ("sched/deadline: Use revised wakeup rule for
> dl_server") applies the revised wakeup rule to any server, as a result
> servers that are not running (dl_defer_running == 0) and start with a
> deadline overflow get enqueued and can boost tasks as if they were
> running, invalidating the defer rule and the documented state model.
>
> Apply the revised wakeup rule only for deferrable servers that are
> marked as running.
>
> Fixes: 14a857056466 ("sched/deadline: Use revised wakeup rule for dl_server")
> Signed-off-by: Gabriele Monaco <gmonaco@redhat.com>
> ---
Makes sense to me.
Acked-by: Juri Lelli <juri.lelli@redhat.com>
Thanks,
Juri
next prev parent reply other threads:[~2026-05-25 6:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 12:58 [PATCH] sched/deadline: Use revised wakeup rule only for running dl_server Gabriele Monaco
2026-05-22 20:58 ` Andrea Righi
2026-05-25 6:19 ` Juri Lelli [this message]
2026-07-29 13:27 ` Gabriele Monaco
2026-07-29 13:29 ` Gabriele Monaco
2026-07-29 14:52 ` Peter Zijlstra
2026-07-29 14:54 ` Gabriele Monaco
2026-07-29 19:18 ` John Stultz
2026-07-30 11:03 ` [tip: sched/urgent] " tip-bot2 for Gabriele Monaco
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=ahPp_pRBb3kGuwpZ@jlelli-thinkpadt14gen4.remote.csb \
--to=juri.lelli@redhat.com \
--cc=arighi@nvidia.com \
--cc=gmonaco@redhat.com \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=soolaugust@gmail.com \
--cc=suzhidao@xiaomi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.