Lines Matching refs:tasks

41 Nodes to a set of tasks.   In this document "Memory Node" refers to
44 Cpusets constrain the CPU and Memory placement of tasks to only
79 the available CPU and Memory resources amongst the requesting tasks.
136  - You can list all the tasks (by pid) attached to any cpuset.
145  - in sched.c migrate_live_tasks(), to keep migrating tasks within
181  - cpuset.sched_relax_domain_level: the searching range when migrating tasks
188 CPUs and Memory Nodes, and attached tasks, are modified by writing
196 on a system into related sets of tasks such that each set is constrained
202 the detailed placement done on individual tasks and memory regions
249 of the rate that the tasks in a cpuset are attempting to free up in
291     set of tasks in the cpuset.
299 the tasks in the cpuset, in units of reclaims attempted per second,
377 tasks.  If one CPU is underutilized, kernel code running on that
378 CPU will look for tasks on other more overloaded CPUs and move those
379 tasks to itself, within the constraints of such placement mechanisms
398 have tasks running on them unless explicitly assigned.
429 When doing this, you don't usually want to leave any unpinned tasks in
430 the top cpuset that might use non-trivial amounts of CPU, as such tasks
437 Of course, tasks pinned to a particular CPU can be left in a cpuset
438 that disables "cpuset.sched_load_balance" as those tasks aren't going anywhere
462 tasks only partially load balanced, just on the overlapping CPUs.
465 don't leave tasks that might use non-trivial amounts of CPU in
525 In sched domain, the scheduler migrates tasks in 2 ways; periodic load
534 And if a CPU run out of tasks in its runqueue, the CPU try to pull
535 extra tasks from other busy CPUs to help them before it is going to
538 Of course it takes some searching cost to find movable tasks and/or
618 if a task's pid is written to another cpusets 'cpuset.tasks' file, then its
633 tasks are attached to that cpuset, any pages that task had
641 'cpuset.mems' file is modified, pages allocated to tasks in that
649 then all the tasks in that cpuset will be moved to the nearest ancestor
650 with non-empty cpus.  But the moving of some (or all) tasks might fail if
652 on task attaching.  In this failing case, those tasks will stay
676     /sys/fs/cgroup/cpuset tasks file for that cpuset.
677  6) fork, exec or clone the job tasks from this founding father task.
689   /bin/echo $$ > tasks
741 cpuset.memory_migrate  tasks
758 # /bin/echo $$ > tasks
813 # /bin/echo PID > tasks
816 If you have several tasks to attach, you have to do it one after another:
818 # /bin/echo PID1 > tasks
819 # /bin/echo PID2 > tasks
821 # /bin/echo PIDn > tasks