Documentation/scheduler/sched-deadline.rst

183       the task's utilization must be removed from the previous runqueue's active
184       utilization and must be added to the new runqueue's active utilization.
192       its utilization is removed from the runqueue's active utilization.
195       its utilization is added to the active utilization of the runqueue where
219   - Umax is the maximum reclaimable utilization (subjected to RT throttling
221   - Uinact is the (per runqueue) inactive utilization, computed as
223   - Uextra is the (per runqueue) extra reclaimable utilization
343  The utilization of a real-time task is defined as the ratio between its
347  If the total utilization U=sum(WCET_i/P_i) is larger than M (with M equal
350  Note that total utilization is defined as the sum of the utilizations
354  Moreover, if the total utilization is larger than M, then we risk starving
356  If, instead, the total utilization is smaller than M, then non real-time
369  utilization[12].
378  of all the tasks executing on a CPU if and only if the total utilization
400  but this cannot be done by comparing the total utilization or density with
434  time t + e + P, after its absolute deadline. The total utilization of the
443  between total utilization (or density) and a fixed constant. If all tasks
455  As seen, enforcing that the total utilization is smaller than M does not
458  a total utilization smaller than M is enough to guarantee that non real-time
463  the total utilization is smaller or equal than M then the response times of
562  correctly schedule a set of real-time tasks is that the total utilization
565  than M. Notice that the ratio runtime/period is equivalent to the utilization
586  interface we can put a cap on total utilization of -deadline tasks (i.e.,