From: Tejun Heo <tj@kernel.org>
To: Fredrik 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: Thu, 16 Apr 2026 07:59:33 -1000 [thread overview]
Message-ID: <aeEjhTftzK_sjYi-@slm.duckdns.org> (raw)
In-Reply-To: <CALP2E1xwgfNmW+u=oyQ6bVW0ZeuQRZK65gR5RXyQyzy1n6U_8Q@mail.gmail.com>
Hello,
On Thu, Apr 16, 2026 at 10:11:16AM +0200, Fredrik Bratberg wrote:
> I understand that this patch undermines the safety aspects taken into the
> design of sched_ext: For example safely returning to the EEVDF scheduler
> if tasks are starved. However, this is a tradeoff which is fine for what I
> am trying to do, and the Kconfig is meant as an "expert" option.
I'm not sure we can include a Kconfig option in the upstream kernel that can
lead to system lockups in everyday scenarios no matter how the option is
marked.
> My goal here is to look into the possibility of creating custom real-time
> policies using sched_ext, where SCHED_EXT tasks could gain priority over
> all other tasks. I am aware that this pushes the boundaries of what
> sched_ext is meant to do, but want to start a discussion on whether this
> could in general be a future feature of sched_ext or not.
In the current form at least, I'm afraid this would have to be carried
outside the tree.
Thanks.
--
tejun
next prev parent reply other threads:[~2026-04-16 17:59 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
2026-04-16 8:11 ` Fredrik Bratberg
2026-04-16 17:59 ` Tejun Heo [this message]
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=aeEjhTftzK_sjYi-@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