Lines Matching full:tasks

6 Core scheduling support allows userspace to define groups of tasks that can
8 group of tasks don't trust another), or for performance usecases (some
20 attacks. It allows HT to be turned on safely by ensuring that only tasks in a
35 Using this feature, userspace defines groups of tasks that can be co-scheduled
37 tasks that are not in the same group never run simultaneously on a core, while
42 well as admission and removal of tasks from created groups::
66     will be performed for all tasks in the task group of ``pid``.
76 Building hierarchies of tasks
86 Transferring a cookie between the current and other tasks is possible using
90 scheduling group and share it with already running tasks.
95 mentioned in `Usage`_, tasks with the same cookie value are assumed to trust
98 The basic idea is that, every schedule event tries to select tasks for all the
99 siblings of a core such that all the selected tasks running on a core are
115 have tasks on its on runqueue to run, however it will still have to run idle.
120 The scheduler tries its best to find tasks that trust each other such that all
121 tasks selected to be scheduled are of the highest priority in a core.  However,
122 it is possible that some runqueues had tasks that were incompatible with the
150 Core scheduling maintains trust relationships amongst groups of tasks by
152 When a system with core scheduling boots, all tasks are considered to trust
155 communicate them. In other words, all tasks have a default cookie value of 0.
157 cookie-0 tasks is also avoided.
159 Once userspace uses the above mentioned interfaces to group sets of tasks, tasks
161 outside. Tasks outside the group also don't trust tasks within.
165 Core scheduling tries to guarantee that only trusted tasks run concurrently on a
166 core. But there could be small window of time during which untrusted tasks run
172 Core scheduling selects only trusted tasks to run together. IPI is used to notify
176 IPI. Even though cache is flushed on entry to user mode, victim tasks on siblings
186 siblings run tasks which trust each other, when the kernel is executing
205 parallelism of the untrusted tasks, it would still solve the above issues while
206 allowing system processes (trusted tasks) to share a core.
221 - Isolating tasks that needs a whole core: Examples include realtime tasks, tasks
223 - Gang scheduling: Requirements for a group of tasks that needs to be scheduled