Lines Matching refs:runtime

42  SCHED_DEADLINE uses three parameters, named "runtime", "period", and
44  "runtime" microseconds of execution time every "period" microseconds, and
45  these "runtime" microseconds are available within "deadline" microseconds
51  task actually receives "runtime" time units within "deadline" if a proper
56  that each task runs for at most its runtime every period, avoiding any
66   - Each SCHED_DEADLINE task is characterised by the "runtime",
70     a "remaining runtime". These two parameters are initially set to 0;
75                  remaining runtime                  runtime
81     remaining runtime are re-initialised as
84          remaining runtime = runtime
86     otherwise, the scheduling deadline and the remaining runtime are
90     remaining runtime is decreased as
92          remaining runtime = remaining runtime - t
94     (technically, the runtime is decreased at every tick, or when the
97   - When the remaining runtime becomes less or equal than 0, the task is
104     throttled task, the scheduling deadline and the remaining runtime are
108          remaining runtime = remaining runtime + runtime
189   - runtime >= WCET
193  IOW, if runtime >= WCET and if period is >= P, then the scheduling deadlines
197  Notice that if runtime > deadline the admission control will surely reject
214  effective and useful (that is, to be able to provide "runtime" time units
223  the sum of the ratio between runtime and period for all tasks is smaller
224  than M. Notice that the ratio runtime/period is equivalent to the utilisation
254  -deadline runtime is accounted against the -rt runtime. We realise that this
274  runtime at each instance, and that is scheduled according to the urgency of
295  and that -deadline tasks will receive their runtime with a guaranteed
299  deterministically guarantee that -deadline tasks will receive their runtime
361  parameters (e.g., niceness, priority, runtime/deadline/period). rt-app