From: Yuri Andriaccio <yurand2000@gmail.com>
To: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Luca Abeni <luca.abeni@santannapisa.it>,
Yuri Andriaccio <yuri.andriaccio@santannapisa.it>
Subject: [PATCH] sched/deadline: Fix replenishment logic for non-deferred servers
Date: Mon, 20 Apr 2026 18:34:10 +0200 [thread overview]
Message-ID: <20260420163410.20808-1-yurand2000@gmail.com> (raw)
A special flag of the deadline entities, the 'dl_defer' flag, is explicitly
documents changing the behaviour of deadline tasks and servers to the special
deferred behaviour that replenishes and unthrottles the linked dl entity just in
time so it does not miss its deadline.
Currently, this behaviour is only used by fair-servers (and ext-servers), while
regular tasks use the original CBS (Constant Bandwidth Server) rules.
The bug (and fix) which follows is of interest to those deadline server entities
which do not request the deferred behaviour (i.e., dl_defer = 0):
whenever a non-deferred deadline entity expends all of its runtime it must start
the replenishment timer or, if the wake-up instant is too close to the current
time, the entity must be simply re-enqueued and its runtime replenished.
Currently, the 'dl_defer' flag is ignored when replenishing any deadline server,
defaulting to the deferred behaviour, while this fix correctly addresses the
issue.
Unfortunately, no testing of this bugfix is possible as there are currently no
deadline servers which use the standard non-deferred behaviour. This bug was
discovered during the development of the Hierarchical CBS patch
(https://lore.kernel.org/all/20251201124205.11169-1-yurand2000@gmail.com/) which
makes extensive use of the non-deferred servers.
Thanks for your support and have a nice day,
Yuri
Signed-off-by: Yuri Andriaccio <yurand2000@gmail.com>
---
kernel/sched/deadline.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
index d08b00429323..19e63d1307b7 100644
--- a/kernel/sched/deadline.c
+++ b/kernel/sched/deadline.c
@@ -1523,8 +1523,12 @@ static void update_curr_dl_se(struct rq *rq, struct sched_dl_entity *dl_se, s64
if (unlikely(is_dl_boosted(dl_se) || !start_dl_timer(dl_se))) {
if (dl_server(dl_se)) {
- replenish_dl_new_period(dl_se, rq);
- start_dl_timer(dl_se);
+ if (dl_se->dl_defer) {
+ replenish_dl_new_period(dl_se, rq);
+ start_dl_timer(dl_se);
+ } else {
+ enqueue_dl_entity(dl_se, ENQUEUE_REPLENISH);
+ }
} else {
enqueue_task_dl(rq, dl_task_of(dl_se), ENQUEUE_REPLENISH);
}
base-commit: f338e77383789c0cae23ca3d48adcc5e9e137e3c
--
2.53.0
reply other threads:[~2026-04-20 16:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260420163410.20808-1-yurand2000@gmail.com \
--to=yurand2000@gmail.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@santannapisa.it \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=yuri.andriaccio@santannapisa.it \
/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