Re: [PATCH v3 6/8] sched: Limit sysctl sched_rt_{period|runtime}_us to RT_GROUP_SCHED
From: Sebastian Andrzej Siewior
Date: Fri Nov 20 2026 - 10:36:31 EST
On 2026-11-20 16:06:55 [+0100], Juri Lelli wrote:
> Hello,
Hi,
> I agree on the RT throttling part. Before this series, writing to them
> does serve a purpose, though. 5/8 moves that functionality to sysfs,
> which leaves the files without a purpose, and 6/8 then removes them. So
> existing users don't lose a useless knob; they lose the working one,
> which has moved somewhere else. LTP is not the only one that will
> notice, I'm afraid.
>
> This is what I meant with "yes and no" in the RFC thread: we need an
> interface for admission control, and I wasn't sure how much breakage
> moving it would cause. Now we have a first data point. :)
>
> You suggested yourself back then to keep the files and make them apply
> to DL only. I think that's something like:
>
> - keep sched_rt_{period,runtime}_us for !RT_GROUP_SCHED, backed by the
> same code as the new dl_{period,runtime}_us (sched_dl_try_boundary()),
> keeping the current validation semantics (the LTP test checks the
> EINVAL cases, and 0 is a valid runtime today)
> - pr_warn_once() on write saying they only control DEADLINE admission
> control and that RT throttling is handled by the fair_server,
> pointing to where its knobs are
> - fix the documentation as you are doing already
>
> That way nobody gets surprised anymore, which was your point, and we
> don't break anyone? We can still discuss deprecating the procfs names
> later, once the new interface has been around for a while maybe?
Doesn't sound bad. Let me respin it with these changes.
Thanks.
> Thanks,
> Juri
Sebastian