Lines Matching refs:placement

44 Cpusets constrain the CPU and Memory placement of tasks to only
48 job placement on large systems.
75 the efficient scheduling and memory placement of processes.
82 memory placement to reduce memory access times and contention,
174  - cpuset.cpu_exclusive flag: is cpu placement exclusive?
175  - cpuset.mem_exclusive flag: is memory placement exclusive?
202 the detailed placement done on individual tasks and memory regions
362 This memory placement policy is also known (in other contexts) as
379 tasks to itself, within the constraints of such placement mechanisms
595 does not support one task updating the memory placement of another
597 or Memory Node placement, or of changing to which cpuset a task
603 in the task's cpuset, and update its per-task memory placement to
604 remain within the new cpusets memory placement.  If the task was using
610 was MPOL_BIND bound to the new cpuset (even though its NUMA placement,
613 memory placement, as above, the next time that the kernel attempts
617 will have its allowed CPU placement changed immediately.  Similarly,
619 allowed CPU placement is changed immediately.  If such a task had been
624 In summary, the memory placement of a task whose cpuset is changed is
626 and the processor placement is updated immediately.
631 cpusets memory placement policy 'cpuset.mems' subsequently changes.
635 to the task's new cpuset. The relative placement of the page within
657 violate cpuset placement, over starving a task that has had all