From: Chris Friesen <cbf123@usask.ca>
To: LKML <linux-kernel@vger.kernel.org>
Subject: [SCHED] any modern replacement for RT_RUNTIME_GREED in the mainline kernel?
Date: Fri, 6 Dec 2024 12:12:57 -0600 [thread overview]
Message-ID: <49a1c1eb-5e80-4eb2-b882-a2df3ec12012@usask.ca> (raw)
Hi all,
Some time back
(https://lore.kernel.org/lkml/fa5b1b55d8934c6a0e02e04a7ad6afdf4012c2e0.1478506194.git.bristot@redhat.com/)
a patch was proposed that would allow high-CPU usage RT tasks to use
100% of the CPU as long as there were no non-RT tasks that wanted to
run, but if a non-RT task did want to run the RT-throttling would kick
in to prevent starvation and deadlocks.
It was rejected for philosophical reasons, with a mention of a
hypothetical deadline server being the "proper" solution.
Has anything been done in this area in the years since then?
Thanks,
Chris
(please CC me on replies, I'm not subscribed to the list)
next reply other threads:[~2024-12-06 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 18:12 Chris Friesen [this message]
2024-12-06 20:30 ` 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=49a1c1eb-5e80-4eb2-b882-a2df3ec12012@usask.ca \
--to=cbf123@usask.ca \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®