Re: [RFC PATCH v7 00/29] Hierarchical Constant Bandwidth Server

From: luca abeni

Date: Thu Nov 19 2026 - 09:42:33 EST


On Thu, 19 Nov 2026 15:36:01 +0100
Juri Lelli <juri.lelli@xxxxxxxxxx> wrote:
> > > > The root has no ancestor to fall back to, so a missing entry
> > > > can't mean anything there. It has to always carry an entry for
> > > > every possible CPU, which defaults to zero, and reject "max":
> > > >
> > > > 0-127 runtime=0 period=1000000
> > >
> > > Also, related to the above: on the root these numbers mean
> > > something else (how much DL bandwidth cgroups may reserve, not a
> > > server for the root's tasks), and showing them in the same file
> > > and format is part of what makes the example misleading. Would
> > > you be OK with dropping cpu.rt.max on the root and exposing the
> > > parameters through a separately named root-only file (or the
> > > existing sysctls)? That way, having no entry all the way up
> > > consistently means unmanaged FIFO/RR, and nothing on the root
> > > looks like a budget those tasks share.
> >
> > Regardless of the filenames we decide, the defaults for these
> > settings indicate the fraction of CPU time that can be consumed by
> > all real-time tasks that are not in the root cgroup, right?
>
> Not quite, I think? They cap the bandwidth that can be reserved for
> cgroup servers, so they only cover RT tasks that are served by one.
> RT tasks in a non-root "max" cgroup (with no configured ancestor) are
> not in the root cgroup, but run in the root runqueue

Ah, right, sorry about the confusion... I was counting them as
belonging to the root cgroup, but you are right, they are in different
cgroups.

So, yes, I was victim of the confusion you'd like to avoid :)



Luca



> and aren't
> limited by those values at all (sched_rt_can_attach() lets them in
> unconditionally). Which is the kind of confusion I'd like the root
> interface to avoid.
>
> Thanks,
> Juri
>