Lines Matching refs:utilization
126 2. Task utilization
134 while task utilization is specific to CFS, it is convenient to describe it here
137 Task utilization is a percentage meant to represent the throughput requirements
142 On an SMP system with fixed frequencies, 100% utilization suggests the task is a
143 busy loop. Conversely, 10% utilization hints it is a small periodic task that
172 The task utilization signal can be made frequency invariant using the following
178 task utilization of 25%.
183 CPU capacity has a similar effect on task utilization in that running an
210 The task utilization signal can be made CPU invariant using the following
217 invariant task utilization of 25%.
219 2.4 Invariant task utilization
222 Both frequency and CPU invariance need to be applied to task utilization in
224 utilization that is both CPU and frequency invariant is thus, for a given
231 In other words, invariant task utilization describes the behaviour of a task as
235 Any mention of task utilization in the following sections will imply its
241 Without a crystal ball, task behaviour (and thus task utilization) cannot
244 Tracking (PELT) mechanism, one of those yielding an *average* utilization (as
248 considering a "true" task utilization (using a crystal ball), the implementation
269 utilization. Architectures must define arch_scale_freq_capacity(cpu) for that
347 Furthermore, uclamp lets userspace specify a minimum and a maximum utilization
356 above. On top of that, uclamp is used to clamp the task utilization values,
362 By using uclamp, userspace can e.g. allow a busy loop (100% utilization) to run
364 periodic task (e.g. 10% utilization) to run on the highest-performance CPUs by
400 utilization estimation)