Lines Matching full:tasks

44 Nodes to a set of tasks.   In this document "Memory Node" refers to
47 Cpusets constrain the CPU and Memory placement of tasks to only
82 the available CPU and Memory resources amongst the requesting tasks.
139  - You can list all the tasks (by pid) attached to any cpuset.
148  - in sched.c migrate_live_tasks(), to keep migrating tasks within
184  - cpuset.sched_relax_domain_level: the searching range when migrating tasks
192 CPUs and Memory Nodes, and attached tasks, are modified by writing
200 on a system into related sets of tasks such that each set is constrained
206 the detailed placement done on individual tasks and memory regions
264 of the rate that the tasks in a cpuset are attempting to free up in
307     set of tasks in the cpuset.
315 the tasks in the cpuset, in units of reclaims attempted per second,
350 instead.    Tasks using mbind() or set_mempolicy() calls to set NUMA
393 tasks.  If one CPU is underutilized, kernel code running on that
394 CPU will look for tasks on other more overloaded CPUs and move those
395 tasks to itself, within the constraints of such placement mechanisms
414 have tasks running on them unless explicitly assigned.
446 When doing this, you don't usually want to leave any unpinned tasks in
447 the top cpuset that might use non-trivial amounts of CPU, as such tasks
454 Of course, tasks pinned to a particular CPU can be left in a cpuset
455 that disables "cpuset.sched_load_balance" as those tasks aren't going anywhere
479 tasks only partially load balanced, just on the overlapping CPUs.
482 don't leave tasks that might use non-trivial amounts of CPU in
543 In sched domain, the scheduler migrates tasks in 2 ways; periodic load
552 And if a CPU run out of tasks in its runqueue, the CPU try to pull
553 extra tasks from other busy CPUs to help them before it is going to
556 Of course it takes some searching cost to find movable tasks and/or
644 if a task's pid is written to another cpuset's 'tasks' file, then its
659 tasks are attached to that cpuset, any pages that task had
667 'cpuset.mems' file is modified, pages allocated to tasks in that
675 then all the tasks in that cpuset will be moved to the nearest ancestor
676 with non-empty cpus.  But the moving of some (or all) tasks might fail if
678 on task attaching.  In this failing case, those tasks will stay
702     /sys/fs/cgroup/cpuset tasks file for that cpuset.
703  6) fork, exec or clone the job tasks from this founding father task.
715   /bin/echo $$ > tasks
771   cpuset.memory_migrate  tasks
792   # /bin/echo $$ > tasks
852   # /bin/echo PID > tasks
855 If you have several tasks to attach, you have to do it one after another::
857   # /bin/echo PID1 > tasks
858   # /bin/echo PID2 > tasks
860   # /bin/echo PIDn > tasks