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

2 Real-Time group scheduling
12      2.1 System-wide settings
33    are real-time processes).
40 ---------------
50 ----------------
53 in a given period. We allocate this "run time" for each realtime group which
56 Any time not allocated to a realtime group will be used to run normal priority
57 tasks (SCHED_OTHER). Any allocated run time not used will also be picked up by
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
77 lack an EDF scheduler to make non-uniform periods usable.
85 ------------------------
101   * sched_rt_runtime_us takes values from -1 to (INT_MAX - 1).
102   * A run time of -1 specifies runtime == period, ie. no limit.
106 ---------------------
110 SCHED_OTHER (non-RT tasks). These defaults were chosen so that a run-away
112 it.  By setting runtime to -1 you'd get the old behaviour back.
115 period from /proc/sys/kernel/sched_rt_period_us and a run time of 0. If you
121 not be able to run realtime tasks as any user other than root until you have
122 done that, even if the user has the rights to run processes with realtime
127 ----------------------------
133 to control the CPU time reserved for each control group.
135 For more information on working with control groups, you should read
136 Documentation/admin-guide/cgroup-v1/cgroups.rst as well.
163 	- this runs for 0.05s once every 0.1s
167 	- this runs for 0.025s twice every 0.1s (or once every 0.05 sec).
169 This means that currently a while (1) loop in A will run for the full period of
180 the limited static priority levels 0-99. With deadline scheduling you need to
182 deadline delta (deadline - now)).
184 This means the whole PI machinery will have to be reworked - and that is one of