From: Tejun Heo <tj@kernel.org>
To: Fredrik Boettger Bratberg <fredrik.b.bratberg@gmail.com>
Cc: Henrik Austad <henrik@austad.us>,
Peter Ziljstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@kernel.org>,
linux-rt-devel@lists.linux.dev, sched-ext@lists.linux.dev
Subject: Re: [RFC PATCH] sched: add CONFIG_SCHED_EXT_RT_EXPERIMENTAL to move SCHED_EXT above SCHED_RR/SCHED_FIFO
Date: Tue, 14 Apr 2026 07:23:02 -1000 [thread overview]
Message-ID: <ad539mUd8A0lDWAw@slm.duckdns.org> (raw)
In-Reply-To: <20260414125933.3520885-1-fredrik.b.bratberg@gmail.com>
Hello,
On Tue, Apr 14, 2026 at 02:59:33PM +0200, Fredrik Boettger Bratberg wrote:
> A recent paper published in the 2025 Real-Time Systems Symposium (RTSS)
> "Enabling Flexible Scheduling in ROS 2", would presumably also benefint
> from this feature. The paper aims to address and improve the real-time
> capabilities of Robot Operating System 2 (ROS2). As part of their paper
> they implement an EDF using sched_ext. They do not explicitly address the
> issue of their EDF SCHED_EXT tasks effectively having a lower priority than
> SCHED_NORMAL, but it is a known limitation of the current sched_ext class
> placement
Isn't that mostly solvable by just not putting tasks in DL/RT and enabling
switching_all?
> This change conditionally reorders sched_class selection such that, when
> enabled:
>
> STOP > DL > EXT > RT > FAIR > IDLE
The problem is that RT being above EXT is required for safety as EXT depends
on RT superceding it for enable/disable path forward progress guarantee. If
you put EXT on top of RT, it's relatively easy to stall out the whole system
without any way to recover it.
Thanks.
--
tejun
next prev parent reply other threads:[~2026-04-14 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 12:59 [RFC PATCH] sched: add CONFIG_SCHED_EXT_RT_EXPERIMENTAL to move SCHED_EXT above SCHED_RR/SCHED_FIFO Fredrik Boettger Bratberg
2026-04-14 17:23 ` Tejun Heo [this message]
2026-04-16 8:11 ` Fredrik Bratberg
2026-04-16 17:59 ` Tejun Heo
2026-04-17 6:30 ` Fredrik Bratberg
2026-09-21 7:47 ` Tengfei Fan
2026-09-28 15:39 ` Christian Loehle
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=ad539mUd8A0lDWAw@slm.duckdns.org \
--to=tj@kernel.org \
--cc=fredrik.b.bratberg@gmail.com \
--cc=henrik@austad.us \
--cc=linux-rt-devel@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sched-ext@lists.linux.dev \
--cc=tglx@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