Lines Matching refs:SCHED_DEADLINE

16    3.4 Relationship with SCHED_DEADLINE Parameters
23    5.1 SCHED_DEADLINE and cpusets HOWTO
40  The SCHED_DEADLINE policy contained inside the sched_dl scheduling class is
52  SCHED_DEADLINE [18] uses three parameters, named "runtime", "period", and
53  "deadline", to schedule tasks. A SCHED_DEADLINE task should receive
76   - Each SCHED_DEADLINE task is characterized by the "runtime",
82   - When a SCHED_DEADLINE task wakes up (becomes ready for execution),
99   - When a SCHED_DEADLINE task executes for an amount of time t, its
289  When cpufreq's schedutil governor is selected, SCHED_DEADLINE implements the
305  * scheduling theory, and how it applies to SCHED_DEADLINE.
445  but the theoretical result that is important for SCHED_DEADLINE is that if
449 3.4 Relationship with SCHED_DEADLINE Parameters
453  SCHED_DEADLINE scheduling parameters described in Section 2 (runtime,
457  SCHED_DEADLINE schedules the tasks according to scheduling deadlines (see
460  are respected, then SCHED_DEADLINE can be used to schedule real-time tasks
557  figure out how we want to manage SCHED_DEADLINE bandwidth at the task group
566  parameters, so that CPU bandwidth is allocated to SCHED_DEADLINE tasks
610  SCHED_DEADLINE task can be retrieved through /proc/<pid>/sched (entries
618  The default value for SCHED_DEADLINE bandwidth is to have rt_runtime equal to
637  When a SCHED_DEADLINE task calls sched_yield(), it gives up its
647  SCHED_DEADLINE tasks.
657 5.1 SCHED_DEADLINE and cpusets HOWTO
700  The SCHED_DEADLINE policy can be easily tested using two applications that
718  The above creates 2 threads. The first one, scheduled by SCHED_DEADLINE,
733  schedtool-dl, which can be used to setup SCHED_DEADLINE parameters for a
741  With this, my_cpuhog_app is put to run inside a SCHED_DEADLINE reservation
752  showing how SCHED_DEADLINE reservations can be created by a real-time
769  #define SCHED_DEADLINE	6
801 	/* SCHED_DEADLINE (nsec) */
837 	attr.sched_policy = SCHED_DEADLINE;