Lines Matching +full:real +full:- +full:time
2 Real-Time group scheduling
12 2.1 System-wide settings
28 resolution, or the time it takes to handle the budget refresh itself.
33 are real-time processes).
40 ---------------
43 the amount of bandwidth (eg. CPU time) being constant. In order to schedule
45 of the CPU time available. Without a minimum guarantee a realtime group can
50 ----------------
52 CPU time is divided by means of specifying how much time can be spent running
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
68 needs only about 3% CPU time to do so, it can do with a 0.03 * 0.005s =
69 0.00015s. So this group can be scheduled with a period of 0.005s and a run time
72 The remaining CPU time will be used for user input and other tasks. Because
73 realtime 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 realtime scheduling may use. Even without
94 CONFIG_RT_GROUP_SCHED enabled, this will limit time reserved to realtime
98 * Time is specified in us because the interface is s32. This gives an
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
111 realtime tasks will not lock up the machine but leave a little time to recover
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
127 ----------------------------
129 Enabling CONFIG_RT_GROUP_SCHED lets you explicitly allocate real
133 to control the CPU time reserved for each control group.
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).
176 get their allocated time.
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