linux-kernel - Re: [SCHED] any modern replacement for RT_RUNTIME

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2ae90276-67f8-4b46-9cc5-1f7062eadfff@arm.com>
Date: Fri, 6 Dec 2024 20:30:05 +0000
From: Christian Loehle <christian.loehle@....com>
To: Chris Friesen <cbf123@...sk.ca>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [SCHED] any modern replacement for RT_RUNTIME_GREED in the
 mainline kernel?

On 12/6/24 18:12, Chris Friesen wrote:
> 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?

There has!
The 'hypothetical deadline server' was implemented and is part
of 6.12
https://lore.kernel.org/lkml/cover.1716811043.git.bristot@kernel.org/