On Tue, Apr 10, 2018 at 06:16:12PM +0100, Patrick Bellasi wrote:
> > I'm not too enthusiastic about util_min/max given that it can easily
> > be read as actual utilization based bandwidth control when what's
> > actually implemented, IIUC, is affecting CPU frequency selection.
> Right now we are basically affecting the frequency selection.
> However, the next step is to use this same interface to possibly bias
> task placement.
> The idea is that:
> - the util_min value can be used to possibly avoid CPUs which have
> a (maybe temporarily) limited capacity, for example, due to thermal
> - a util_max value can use used to possibly identify tasks which can
> be co-scheduled together in a (maybe) limited capacity CPU since
> they are more likely "less important" tasks.
> Thus, since this is a new user-space API, we would like to find a
> concept which is generic enough to express the current requirement but
> also easily accommodate future extensions.
I'm not sure we can overload the meanings like that on the same
interface. Right now, it doesn't say anything about bandwidth (or
utilization) allocation. It just limits the frequency range the
particular cpu that the task ended up on can be in and what you're
describing above is the third different thing. It doesn't seem clear
that they're something which can be overloaded onto the same
> > Maybe something like cpu.freq.min/max are better names?
> IMO this is something too much platform specific.
> I agree that utilization is maybe too much an implementation detail,
> but perhaps this can be solved by using a more generic range.
> What about using values in the [0..100] range which define:
> a percentage of the maximum available capacity
> for the CPUs in the target system
> Do you think this can work?
Yeah, sure, it's more that right now the intention isn't clear. A
cgroup control knob which limits cpu frequency range while the cgroup
is on a cpu is a very different thing from a cgroup knob which
restricts what tasks can be scheduled on the same cpu. They're
actually incompatible. Doing the latter actively breaks the former.
> > This is a problem which exists for all other interfaces. For
> > historical and other reasons, at least till now, we've opted to put
> > everything at system level outside of cgroup interface. We might
> > change this in the future and duplicate system-level information and
> > interfaces in the root cgroup but we wanna do that in a more systemtic
> > fashion than adding an one-off knob in the cgroup root.
> I see, I think we can easily come up with a procfs/sysfs interface
> usable to define system-wide values.
> Any suggestion for something already existing which I can use as a
Most system level interfaces are there with a long history and things
aren't that consistent. One route could be finding an interface
implementing a nearby feature and staying consistent with that.
> > Tying creation / config operations to the config propagation doesn't
> > work well with delegation and is inconsistent with what other
> > controllers are doing. For cases where the propagated config being
> > visible in a sub cgroup is necessary, please add .effective files.
> I'm not sure to understand this point: you mean that we should not
> enforce "consistency rules" among parent-child groups?
You should. It just shouldn't make configurations fail cuz that ends
up breaking delegations.
> I have to look better into this "effective" concept.
> Meanwhile, can you make a simple example?
There's a recent cpuset patchset posted by Waiman Long. Googling for
lkml cpuset and Waiman Long should find it easily.
> > > Tasks on a subgroup can only be more boosted and/or capped, which is
> > Less boosted. .low at a parent level must set the upper bound of .low
> > that all its descendants can have.
> Is that a mandatory requirement? Or based on a proper justification
> you can also accept what I'm proposing?
> I've always been more of the idea that what I'm proposing could make
> more sense for a general case but perhaps I just need to go back and
> better check the use-cases we have on hand to see if it's really
> required or not.
Yeah, I think we want to stick to that semantics. That's what memory
controller does and it'd be really confusing to flip the directions on