From: Peter Zijlstra <peterz@infradead.org>
To: Gabriele Monaco <gmonaco@redhat.com>
Cc: linux-kernel@vger.kernel.org, Juri Lelli <juri.lelli@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Clark Williams <williams@redhat.com>
Subject: Re: [RFC PATCH] sched/deadline: Avoid dl_server boosting with expired deadline
Date: Tue, 14 Oct 2025 11:54:07 +0200 [thread overview]
Message-ID: <20251014095407.GM4067720@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20251007122904.31611-1-gmonaco@redhat.com>
On Tue, Oct 07, 2025 at 02:29:04PM +0200, Gabriele Monaco wrote:
> Recent changes to the deadline server leave it running when the system
> is idle. If the system is idle for longer than the dl_server period and
> the first scheduling occurs after a fair task wakes up, the algorithm
> picks the server as the earliest deadline (in the past) and that boosts
> the fair task that just woke up while:
> * the deadline is in the past
> * the server consumed all its runtime (in background)
> * there is no starvation (idle for about a period)
>
> Prevent the server from boosting a task when the deadline is in the
> past. Instead, replenish a new period and start the server as deferred.
>
> Fixes: 4ae8d9aa9f9d ("sched/deadline: Fix dl_server getting stuck")
> To: Juri Lelli <juri.lelli@redhat.com>
> Cc: Clark Williams <williams@redhat.com>
> Signed-off-by: Gabriele Monaco <gmonaco@redhat.com>
> ---
>
> This behaviour was observed using the RV monitors in [1] and the patch
> was validated on an adapted version of the models. The models are not
> exhaustively validating the dl_server behaviour.
>
> [1] - https://lore.kernel.org/lkml/20250919140954.104920-21-gmonaco@redhat.com
>
> kernel/sched/deadline.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
> index 72c1f72463c7..b3e3d506a18d 100644
> --- a/kernel/sched/deadline.c
> +++ b/kernel/sched/deadline.c
> @@ -2371,6 +2371,17 @@ static struct task_struct *__pick_task_dl(struct rq *rq)
> dl_server_stop(dl_se);
> goto again;
> }
> + /*
> + * If the CPU was idle for long enough time and wakes up
> + * because of a fair task, the dl_server may run after its
> + * period elapsed. Replenish a new period as deferred, since we
> + * are clearly not handling starvation here.
> + */
> + if (dl_time_before(dl_se->deadline, rq_clock(rq))) {
> + dl_se->dl_defer_running = 0;
> + replenish_dl_new_period(dl_se, rq);
> + goto again;
> + }
> rq->dl_server = dl_se;
> } else {
> p = dl_task_of(dl_se);
>
I'm a bit confused, should not enqueue ensure deadline is in the future?
And if it doesn't shouldn't we fix the enqueue path somewhere?
next prev parent reply other threads:[~2025-10-14 9:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 12:29 Gabriele Monaco
2025-10-14 9:30 ` Gabriele Monaco
2025-10-14 9:54 ` Peter Zijlstra [this message]
2025-10-14 10:05 ` Gabriele Monaco
2025-10-14 10:25 ` Peter Zijlstra
2025-10-14 15:32 ` Gabriele Monaco
2025-10-14 16:01 ` Juri Lelli
2025-10-14 19:33 ` Peter Zijlstra
2025-10-15 5:40 ` Juri Lelli
2025-10-20 14:11 ` Peter Zijlstra
2025-10-22 10:11 ` Gabriele Monaco
2025-10-30 18:42 ` Peter Zijlstra
2025-10-31 13:05 ` Peter Zijlstra
2025-10-31 13:24 ` Gabriele Monaco
2025-10-31 15:20 ` Peter Zijlstra
2025-10-31 15:41 ` Gabriele Monaco
2025-10-31 15:44 ` Peter Zijlstra
2025-10-31 15:51 ` Gabriele Monaco
2025-11-01 0:00 ` Peter Zijlstra
2025-11-11 9:58 ` Gabriele Monaco
2025-11-11 11:17 ` Peter Zijlstra
2025-11-11 11:24 ` Peter Zijlstra
2025-11-11 11:37 ` [tip: sched/core] sched/deadline: Fix dl_server stop condition tip-bot2 for Peter Zijlstra
2025-11-01 0:08 ` [RFC PATCH] sched/deadline: Avoid dl_server boosting with expired deadline Peter Zijlstra
2025-11-01 8:43 ` Gabriele Monaco
2025-11-11 11:37 ` [tip: sched/core] sched/deadline: Fix dl_server time accounting tip-bot2 for 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=20251014095407.GM4067720@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=gmonaco@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=williams@redhat.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®