Re: [PATCH 4/7] sched/core: uclamp: add utilization clamping to the CPU controller
From: Tejun Heo
Date: Thu Apr 26 2018 - 14:58:57 EST
On Sat, Apr 21, 2018 at 02:08:30PM -0700, Joel Fernandes wrote:
> Actually no, its not about overloading them. What's Patrick is
> defining here is a property/attribute. What that attribute is used for
> (the algorithms that use it) are a different topic. Like, it can be
> used by the frequency selection algorithms or the task placement
> algorithm. There are multiple algorithms that can use the property. To
> me, this part of the patch makes sense. Maybe it should really be
> called "task_size" or something, since that's what it really is.
I understand that the interface can encode certain intentions and then
there can be different strategies to implement that, but the two
things mentioned here seem fundamentally different to declare them to
be two different implementations of the same intention.
> > 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
> > different controllers.
> What about the .high ? I think there was some confusion about how to
> define that for subgroups. It could perhaps be such that the .high of
> parent is the lower bound of the .high on child but then I'm not sure
> if that fits well with the delegation policies...
The basic rule is simple. A child can never obtain more than its