Lines Matching refs:effective

132 frequency selection as well as task placement to be most effective. Both of
153 and on dequeue it is decremented. This makes keeping track of the effective
156 As tasks are enqueued and dequeued, we keep track of the current effective
160 Later at any path that wants to identify the effective uclamp value of the rq,
161 it will simply need to read this effective uclamp value of the rq at that exact
167 When a task wakes up, the scheduler will look at the current effective uclamp
173 at the current effective uclamp value of the rq which is influenced by the set
210 To reduce the search space when trying to decide the effective uclamp value of
241 The rq then keeps track of its current effective uclamp value for each
301 the actual applied (effective) value can be influenced by more than just the
304 The effective util clamp value of any task is restricted as follows:
314 For now suffice to say that if a task makes a request, its actual effective
388   In a cgroup hierarchy, effective cpu.uclamp.min is the max of (child,
397   In a cgroup hierarchy, effective cpu.uclamp.max is the min of (child,
446 which means that permitted effective UCLAMP_MIN range for tasks is [0:1024].
459 which means that permitted effective UCLAMP_MAX range for tasks is [0:1024].
461 By changing it to 512 for example the effective allowed range reduces to
692 then the effective UCLAMP_MAX for the CPU will be 1024 according to max