Lines Matching refs:period

46  SCHED_DEADLINE uses three parameters, named "runtime", "period", and
48  "runtime" microseconds of execution time every "period" microseconds, and
50  from the beginning of the period.  In order to implement this behavior,
60  that each task runs for at most its runtime every period, avoiding any
71     "deadline", and "period" parameters;
81         scheduling deadline - current time           period
111          scheduling deadline = scheduling deadline + period
144  A real-time task can be periodic with period P if r_{j+1} = r_j + P, or
151  WCET and its period (or minimum inter-arrival time), and represents
227  CPUs, with the first task Task_1=(P,P,P) having period, relative deadline
230  period smaller than the one of the first task. Hence, if all the tasks
270  deadline and period) and the real-time task parameters (WCET, D, P)
282   - period <= P
284  IOW, if runtime >= WCET and if period is <= P, then the scheduling deadlines
347  the sum of the ratio between runtime and period for all tasks is smaller
348  than M. Notice that the ratio runtime/period is equivalent to the utilization
420  worst-case delay respect to the "deadline" parameter. If "deadline" = "period"
424  in a period.
485  parameters (e.g., niceness, priority, runtime/deadline/period). rt-app