Lines Matching refs:placement

47 Cpusets constrain the CPU and Memory placement of tasks to only
51 job placement on large systems.
78 the efficient scheduling and memory placement of processes.
85 memory placement to reduce memory access times and contention,
177  - cpuset.cpu_exclusive flag: is cpu placement exclusive?
178  - cpuset.mem_exclusive flag: is memory placement exclusive?
206 the detailed placement done on individual tasks and memory regions
378 This memory placement policy is also known (in other contexts) as
395 tasks to itself, within the constraints of such placement mechanisms
616 does not support one task updating the memory placement of another
618 or Memory Node placement, or of changing to which cpuset a task
624 in the task's cpuset, and update its per-task memory placement to
625 remain within the new cpusets memory placement.  If the task was using
631 was MPOL_BIND bound to the new cpuset (even though its NUMA placement,
634 memory placement, as above, the next time that the kernel attempts
638 will have its allowed CPU placement changed immediately.  Similarly,
640 allowed CPU placement is changed immediately.  If such a task had been
645 In summary, the memory placement of a task whose cpuset is changed is
647 and the processor placement is updated immediately.
652 cpusets memory placement policy 'cpuset.mems' subsequently changes.
656 to the task's new cpuset. The relative placement of the page within
678 violate cpuset placement, over starving a task that has had all