Lines Matching full:utilization
333 * will not touch the rq's active utilization, in dl_rq_change_utilization()
381 * The utilization of a task cannot be immediately removed from
382 * the rq active utilization (running_bw) when the task blocks.
392 * task's utilization has to be added to running_bw again.
398 * "ACTIVE" when its utilization contributes to running_bw; an
465 * utilization now, instead of starting a timer in task_non_contending()
518 * will not touch the rq's active utilization, in task_contending()
525 * task's utilization has already been removed from in task_contending()
526 * active utilization (either when the task blocked, in task_contending()
1431 * where u is the utilization of the task, Umax is the maximum reclaimable
1432 * utilization, Uinact is the (per-runqueue) inactive utilization, computed
1433 * as the difference between the "total runqueue utilization" and the
1434 * "runqueue active utilization", and Uextra is the (per runqueue) extra
1435 * reclaimable utilization.
2042 * However, the active utilization does not depend on the fact in enqueue_dl_entity()
2045 * In other words, even if a task is throttled its utilization must in enqueue_dl_entity()
2046 * be counted in the active utilization; hence, we need to call in enqueue_dl_entity()
2107 * decrease the active utilization, if needed) in two cases: in dequeue_dl_entity()
2304 * will not touch the rq's active utilization, in migrate_task_rq_dl()
3303 * utilization decreases, we should delay the total in sched_dl_overflow()
3304 * utilization change until the task's 0-lag point. in sched_dl_overflow()
3314 * Do not decrease the total deadline utilization here, in sched_dl_overflow()