Re: [RFC PATCH v7 00/29] Hierarchical Constant Bandwidth Server
From: luca abeni
Date: Fri Nov 20 2026 - 15:24:36 EST
Hi Tejun,
On Fri, 20 Nov 2026 01:55:31 -1000
Tejun Heo <tj@xxxxxxxxxx> wrote:
[...]
> > Yes, I think this is OK. It means that hierarchical scheduling is
> > disabled by default, and the administrator has to write something in
> > the root cgroup to enable it.
>
> That's not what I meant. With the root at "max", nothing has to be
> written to the root. A cgroup can be given a budget right away and
> the budget is admitted against the DL bandwidth directly. An entry on
> the root is only needed to set aside bandwidth for cgroups up front.
Uhm... I think this might be problematic.
The SCHED_DEADLINE admission control for tasks is based on a "global
scheduling" assumption (tasks are free to migrate on all the CPU cores
of the root domain). Hence, the admission control is something like
sum_i(runtime_i/period_i) < limit
But the deadline entities serving the real-time tasks in a cgroup are
pinned to cores (one dl entity serves the cgroup's RT rq for a core).
So, they cannot just be added to the sum mentioned above (which works
for dl entities which are free to migrate).
This issue was solved by reserving a fraction of the CPU time (and the
root cgroup parameters indicated this fraction) to RT cgropus, so that
the SCHED_DEADLINE admission control is still the same (we just decrease
"limit" by the fraction reserved to RT cgroups).
I am not sure about how to adapt this admission test to the strategy
you propose above.
Luca