Lines Matching +full:run +full:- +full:control

2 Real-Time group scheduling
12      2.1 System-wide settings
33    are real-time processes).
40 ---------------
42 Real-time scheduling is all about determinism, a group has to be able to rely on
44 multiple groups of real-time tasks, each group must be assigned a fixed portion
45 of the CPU time available.  Without a minimum guarantee a real-time group can
50 ----------------
53 in a given period. We allocate this "run time" for each real-time group which
54 the other real-time groups will not be permitted to use.
56 Any time not allocated to a real-time group will be used to run normal priority
57 tasks (SCHED_OTHER). Any allocated run time not used will also be picked up by
60 Let's consider an example: a frame fixed real-time renderer must deliver 25
63 time dedicated for the graphics. We can then give this group a run time of 0.8
66 This way the graphics group will have a 0.04s period with a 0.032s run time
69 0.00015s. So this group can be scheduled with a period of 0.005s and a run time
73 real-time tasks have explicitly allocated the CPU time they need to perform
77 lack an EDF scheduler to make non-uniform periods usable.
85 ------------------------
93   A global limit on how much time real-time scheduling may use. This is always
95   period_us for the real-time tasks. Without CONFIG_RT_GROUP_SCHED enabled,
96   this only serves for admission control of deadline tasks. With
98   all real-time groups.
103   * sched_rt_runtime_us takes values from -1 to sched_rt_period_us.
104   * A run time of -1 specifies runtime == period, ie. no limit.
111 ---------------------
115 SCHED_OTHER (non-RT tasks). These defaults were chosen so that a run-away
116 real-time tasks will not lock up the machine but leave a little time to recover
117 it.  By setting runtime to -1 you'd get the old behaviour back.
120 period from /proc/sys/kernel/sched_rt_period_us and a run time of 0. If you
124 Real-time group scheduling means you have to assign a portion of total CPU
125 bandwidth to the group before it will accept real-time tasks. Therefore you will
126 not be able to run real-time tasks as any user other than root until you have
127 done that, even if the user has the rights to run processes with real-time
132 ----------------------------
138 to control the CPU time reserved for each control group.
140 For more information on working with control groups, you should read
141 Documentation/admin-guide/cgroup-v1/cgroups.rst as well.
168 	- this runs for 0.05s once every 0.1s
172 	- this runs for 0.025s twice every 0.1s (or once every 0.05 sec).
174 This means that currently a while (1) loop in A will run for the full period of
185 the limited static priority levels 0-99. With deadline scheduling you need to
187 deadline delta (deadline - now)).
189 This means the whole PI machinery will have to be reworked - and that is one of