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

From: Tejun Heo

Date: Wed Nov 18 2026 - 03:07:13 EST


Hello, Yuri.

The summary sounds fine for the most part. Some comments below.

On Wed, Nov 11, 2026 at 06:56:57PM +0100, Yuri Andriaccio wrote:
> - `cpu.rt.max` only accepts per-CPU settings, so the global "default" is
> removed. Removing all overrides means the cgroup is a "max" cgroup, while
> just a single override means that the cgroup has its own budget.
> + This new interface disallows zero-runtime overrides, as a zero override
> is equal to an empty override when there is at least one non-zero override.
> As an example: [<CPU0 10ms 100ms>, <CPU1 0ms 100ms>] is equal to just
> having [<CPU0 10ms 100ms>]. This seems a bit odd, how to make this better?

It's odd because a missing entry means "max" when there are no entries
and zero when there are some. Can a missing entry always mean "max",
per CPU? On a CPU that a cgroup has no entry for, its tasks would be
served by the nearest ancestor which has one. Zero then becomes a
regular value which is shown on read, and the two configs in your
example are different. The former can't run RT tasks on CPU1. The
latter runs them on the ancestor's budget there.

This means that a cgroup can have its own budget on some CPUs and be
"max" on the others. That is a fundamental part of the interface, so I
think it's best to get it right from the get-go rather than starting
with a restriction.

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

> - `cpu` and `cpuset` controllers are decoupled, as it was before the `cpuset`
> integration patch. The user/admin is responsible for inconsistencies between
> the two controllers (i.e. empty intersection between active server in the
> rt-cgroup and the allowed cpuset just disallows executing RT tasks entirely).

Yes, let's decouple them. With that, can the CPU offline lockout go
away too? An entry for an offline CPU can stay configured and take
effect again when the CPU comes back.

One more thing on the unprivileged FIFO/RR tasks in cgroups. No other
cgroup resource config grants privileges that way. e.g. If an rlimit is
set on memory, memory.low doesn't do anything to work around it. I
think who can use RT policies should be left to system configuration,
i.e. RLIMIT_RTPRIO and CAP_SYS_NICE. Can you drop that patch?

Thanks.

--
tejun