Lines Matching refs:SCHED_DEADLINE

16    5.1 SCHED_DEADLINE and cpusets HOWTO
33  The SCHED_DEADLINE policy contained inside the sched_dl scheduling class is
42  SCHED_DEADLINE uses three parameters, named "runtime", "period", and
43  "deadline", to schedule tasks. A SCHED_DEADLINE task should receive
66   - Each SCHED_DEADLINE task is characterised by the "runtime",
72   - When a SCHED_DEADLINE task wakes up (becomes ready for execution),
89   - When a SCHED_DEADLINE task executes for an amount of time t, its
117  * scheduling theory, and how it applies to SCHED_DEADLINE.
185  SCHED_DEADLINE can be used to schedule real-time tasks guaranteeing that
234  figure out how we want to manage SCHED_DEADLINE bandwidth at the task group
243  parameters, so that CPU bandwidth is allocated to SCHED_DEADLINE tasks
290  The default value for SCHED_DEADLINE bandwidth is to have rt_runtime equal to
312 5.1 SCHED_DEADLINE and cpusets HOWTO
354  The SCHED_DEADLINE policy can be easily tested using two applications that
372  The above creates 2 threads. The first one, scheduled by SCHED_DEADLINE,
387  schedtool-dl, which can be used to setup SCHED_DEADLINE parameters for a
395  With this, my_cpuhog_app is put to run inside a SCHED_DEADLINE reservation
406  showing how SCHED_DEADLINE reservations can be created by a real-time
423  #define SCHED_DEADLINE	6
455 	/* SCHED_DEADLINE (nsec) */
491 	attr.sched_policy = SCHED_DEADLINE;