Lines Matching refs:its

54 include CPUs in its CPU affinity mask, and using the mbind(2) and
55 set_mempolicy(2) system calls to include Memory Nodes in its memory
58 schedule a task on a CPU that is not allowed in its cpus_allowed
142  - in fork and exit, to attach and detach a task from its cpuset.
187 command.  The properties of a cpuset, such as its flags, allowed
207  - Its CPUs and Memory Nodes must be a subset of its parents.
208  - It can't be marked exclusive unless its parent is.
209  - If its cpu or memory is exclusive, they may not overlap any sibling.
238 isolating each job's user allocation in its own cpuset.  To do this,
382 The algorithmic cost of load balancing and its impact on key shared
450 a task to a CPU outside its cpuset, but the scheduler load balancing
456 will get balancing across all its CPUs, but if it disables the flag,
461 one of them has this flag enabled, then the other may find its
518 partition requested with the current, and updates its sched domains,
534 And if a CPU run out of tasks in its runqueue, the CPU try to pull
546 woken task B from X to Z since it is out of its searching range.
596 task directly, the impact on a task of changing its cpuset CPU
600 If a cpuset has its Memory Nodes modified, then for each task attached
603 in the task's cpuset, and update its per-task memory placement to
606 its new cpuset, then the task will continue to use whatever subset
608 was using MPOL_BIND and now none of its MPOL_BIND nodes are allowed
610 was MPOL_BIND bound to the new cpuset (even though its NUMA placement,
616 If a cpuset has its 'cpuset.cpus' modified, then each task in that cpuset
617 will have its allowed CPU placement changed immediately.  Similarly,
618 if a task's pid is written to another cpusets 'cpuset.tasks' file, then its
620 bound to some subset of its cpuset using the sched_setaffinity() call,
621 the task will be allowed to run on any CPU allowed in its new cpuset,
634 allocated to it on nodes in its previous cpuset are migrated
658 its allowed CPUs or Memory Nodes taken offline.
675  5) Attach that task to the new cpuset by writing its pid to the
745 it, its properties.  By writing to these files you can manipulate