Lines Matching refs:SCHED_DEADLINE

14    3.4 Relationship with SCHED_DEADLINE Parameters
20    5.1 SCHED_DEADLINE and cpusets HOWTO
37  The SCHED_DEADLINE policy contained inside the sched_dl scheduling class is
46  SCHED_DEADLINE uses three parameters, named "runtime", "period", and
47  "deadline", to schedule tasks. A SCHED_DEADLINE task should receive
70   - Each SCHED_DEADLINE task is characterized by the "runtime",
76   - When a SCHED_DEADLINE task wakes up (becomes ready for execution),
93   - When a SCHED_DEADLINE task executes for an amount of time t, its
121  * scheduling theory, and how it applies to SCHED_DEADLINE.
261  but the theoretical result that is important for SCHED_DEADLINE is that if
265 3.4 Relationship with SCHED_DEADLINE Parameters
269  SCHED_DEADLINE scheduling parameters described in Section 2 (runtime,
273  SCHED_DEADLINE schedules the tasks according to scheduling deadlines (see
276  are respected, then SCHED_DEADLINE can be used to schedule real-time tasks
358  figure out how we want to manage SCHED_DEADLINE bandwidth at the task group
367  parameters, so that CPU bandwidth is allocated to SCHED_DEADLINE tasks
414  The default value for SCHED_DEADLINE bandwidth is to have rt_runtime equal to
436 5.1 SCHED_DEADLINE and cpusets HOWTO
478  The SCHED_DEADLINE policy can be easily tested using two applications that
496  The above creates 2 threads. The first one, scheduled by SCHED_DEADLINE,
511  schedtool-dl, which can be used to setup SCHED_DEADLINE parameters for a
519  With this, my_cpuhog_app is put to run inside a SCHED_DEADLINE reservation
530  showing how SCHED_DEADLINE reservations can be created by a real-time
547  #define SCHED_DEADLINE	6
579 	/* SCHED_DEADLINE (nsec) */
615 	attr.sched_policy = SCHED_DEADLINE;