Lines Matching full:tasks

12 of tasks. It was introduced in v5.3 release. The CGroup support was merged in
16 performance requirements and restrictions of the tasks, thus it helps the
35 One can tell the system (scheduler) that some tasks require a minimum
37 can tell the system that some tasks should be restricted from consuming too
45 dropped. It can also dynamically 'prime' up these tasks if it knows in the
56 Another example is in Android where tasks are classified as background,
58 resources background tasks are consuming by capping the performance point they
59 can run at. This constraint helps reserve resources for important tasks, like
63 background tasks to stay on the little cores which will ensure that:
65         1. The big cores are free to run top-app tasks immediately. top-app
66            tasks are the tasks the user is currently interacting with, hence
67            the most important tasks in the system.
69            are CPU intensive tasks.
89 higher frequency required for the tasks to finish their work in time. Setting
90 UCLAMP_MIN=1024 will ensure such tasks will always see the highest performance
102 In the SCHED_FIFO/RR case, uclamp gives the option to run RT tasks at any
106 Note that by design RT tasks don't have per-task PELT signal and must always
112 MAX for all RT tasks.
115 :ref:`3.4.1 <sched-util-clamp-min-rt-default>` on how to change RT tasks
137 affected by the uclamp settings of all the tasks enqueued on it. For example if
140 enqueued tasks.
142 To be able to aggregate the util clamp value of all the tasks attached to the
150 task on the rq to only a subset of tasks on the top-most bucket.
156 As tasks are enqueued and dequeued, we keep track of the current effective
174 of tasks currently enqueued there and select the appropriate frequency that
211 an rq as tasks are enqueued/dequeued, the whole utilization range is divided
270 When multiple tasks are attached to the same rq, then util clamp must make sure
274 For example, if there are multiple tasks attached to an rq with the following
446 which means that permitted effective UCLAMP_MIN range for tasks is [0:1024].
448 to restrict how much boosting tasks are allowed to acquire.
450 Requests from tasks to go above this knob value will still succeed, but
459 which means that permitted effective UCLAMP_MAX range for tasks is [0:1024].
471 Requests from tasks to go above this knob value will still succeed, but they
481 By default all SCHED_NORMAL/SCHED_OTHER tasks are initialized to:
492 For SCHED_FIFO/SCHED_RR tasks:
500 the system which retains the historical behavior of the RT tasks.
502 RT tasks default uclamp_min value can be modified at boot or runtime via
510 Running RT tasks at maximum performance point is expensive on battery powered
512 guarantees for these tasks without pushing it all the way to maximum
543 4.1. Boost important and DVFS-latency-sensitive tasks
563 4.2. Cap background tasks
567 UCLAMP_MAX for some background tasks that don't care about performance but
573 sched_util_clamp_max system wide interface can be used to limit all tasks from
622 the rq will depend on the actual utilization value of the tasks.
639 when severely capped tasks share the rq with a small non capped task.
734 jumping between frequencies depending on the order tasks wake up, and their