Re: [RFC PATCH v7 00/29] Hierarchical Constant Bandwidth Server
From: Tejun Heo
Date: Fri Nov 20 2026 - 06:55:41 EST
Hello, Luca.
On Fri, Nov 20, 2026 at 12:06:59PM +0100, luca abeni wrote:
> In other words, if tasks can migrate between cores, performance
> guarantees should be "per-cgroup", not per-CPU, which makes it
> difficult to mix "(runtime, period)" and "max" in the same cgroup.
Thanks for the example. I can see that the mixed config is difficult
to analyze. What I don't follow is why the kernel has to enforce it.
Again, this is purely from the interface POV, but wouldn't it be
enough for the kernel to provide the mechanism and leave what gets
built on top of it to the users?
> I do not know much about IO device and io.max, sorry... But maybe the
> difference is that tasks do not "migrate" between different devices?
Yeah, that's different, so the analogy isn't perfect. The allocation
side isn't different tho. One can construct an analogous, if
contorted, case with block devices. e.g. Imagine multiple disks
serving an identical read-only data set, with io.max used for
bandwidth and performance isolation. A workload which moves across
the disks would be essentially the same model as threads moving
across CPUs.
> I also fear this kind of solution can increase the probability of
> misconfiguring the system (ending up with the feature not being used).
I'm not sure baking the constraint into the interface would make
people use it more.
> 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.
Thanks.
--
tejun