Lines Matching full:time
2 Real-Time group scheduling
28 resolution, or the time it takes to handle the budget refresh itself.
33 are real-time processes).
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
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
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
102 * A run time of -1 specifies runtime == period, ie. no limit.
111 realtime tasks will not lock up the machine but leave a little time to recover
115 period from /proc/sys/kernel/sched_rt_period_us and a run time of 0. If you
133 to control the CPU time reserved for each control group.
176 get their allocated time.