Lines Matching full:allowed

61 schedule a task on a CPU that is not allowed in its cpus_allowed
63 node that is not allowed in the requesting task's mems_allowed vector.
122  - Cpusets are sets of allowed CPUs and Memory Nodes, known to the
127    allowed in that task's cpuset.
129    those Memory Nodes allowed in that task's cpuset.
147    allowed in that task's cpuset.
149    the CPUs allowed by their cpuset, if possible.
151    Memory Nodes by what's allowed in that task's cpuset.
152  - in page_alloc.c, to restrict memory to allowed nodes.
181  - cpuset.memory_spread_page flag: if set, spread page cache evenly on allowed nodes
191 command.  The properties of a cpuset, such as its flags, allowed
202 may be re-attached to any other cpuset, if allowed by the permissions
257 interrupt handlers, is allowed to be taken outside even a
274 are trying to use more memory than allowed on the nodes assigned to them,
277 goals if they start to use more memory than allowed to them.
328 over all the nodes that the faulting task is allowed to use, instead
334 faulting task is allowed to use, instead of preferring to put those
427 setting), it requests that all the CPUs in that cpusets allowed 'cpuset.cpus'
477 If two cpusets have partially overlapping 'cpuset.cpus' allowed, and only
484 constrained to some subset of the CPUs allowed to them, for lack of
510 of CPUs allowed to a cpuset having 'cpuset.sched_load_balance' enabled.
633 of MPOL_BIND nodes are still allowed in the new cpuset.  If the task
634 was using MPOL_BIND and now none of its MPOL_BIND nodes are allowed
643 will have its allowed CPU placement changed immediately.  Similarly,
645 allowed CPU placement is changed immediately.  If such a task had been
647 the task will be allowed to run on any CPU allowed in its new cpuset,
684 its allowed CPUs or Memory Nodes taken offline.