Lines Matching refs:that

15 programming interface that a NUMA-aware application can take advantage of.  When
27     is the policy that governs all page allocations that aren't controlled
37     on behalf of the task that aren't controlled by a more specific scope.
38     If a task does not define a task policy, then all page allocations that
46 	executable image that has no awareness of memory policy.  See the
48 	that a task may use to set/change its task/process policy.
51 	[Linux kernel task] that installs the policy and any threads
52 	subsequently created by that thread.  Any sibling threads existing
67     A VMA policy will govern the allocation of pages that back this region of
68     the address space.  Any regions of the task's address space that don't
83 	VMA policies are shared between all tasks that share a virtual address
99 	the mbind() system call, so that page contents can be moved to match
105     the mbind() system call specifying a range of virtual addresses that map
108     apply directly to the shared object.  Thus, all tasks that attach to the
125 	private mappings that have not yet been written by the task, follow
130 	the task that installs the policy for each range of distinct policy.
131 	Thus, different tasks that attach to a shared memory segment can have
132 	different VMA configurations mapping that one shared object.  This
167 	MPOL_BIND:  This mode specifies that memory must come from the
169 	the node in the set with sufficient free memory that is closest to
172 	MPOL_PREFERRED:  This mode specifies that the allocation should be
173 	attempted from the single node specified in the policy.  If that
182 	    policy can be viewed as a Preferred policy that starts at the node
185 	    It is possible for the user to specify that local allocation is
191 	MPOL_INTERLEAVED:  This mode specifies that page allocations be
217 	MPOL_F_STATIC_NODES:  This flag specifies that the nodemask passed by
224 	    allowed nodes.  This may result in nodes being used that were
232 	    For example, consider a task that is attached to a cpuset with
233 	    mems 1-3 that sets an Interleave policy over the same set.  If
237 	    occurs over that node.  If no nodes from the user's nodemask are
242 	    MPOL_PREFERRED policies that were created with an empty nodemask
245 	MPOL_F_RELATIVE_NODES:  This flag specifies that the nodemask passed
248 	and if the allowed nodes changes, then that original nodemask will
260 	    With this flag, the remap is done so that the node numbers from
268 	    If the user's nodemask includes nodes that are outside the range
274 	    For example, consider a task that is attached to a cpuset with
275 	    mems 2-5 that sets an Interleave policy over the same set with
287 	    set of memory nodes allowed by the task's cpuset, as that may
292 	    MPOL_PREFERRED policies that were created with an empty nodemask
304 to '1', representing the reference held by the task that is installing the
319    path".  Note that for MPOL_BIND, the "usage" extends across the entire
339    policy requires that the mmap_sem be held for write, the policy can't be
347    policy management structure.  This requires that we drop this extra
369 	Note:  the headers that define these APIs and the parameter data types
370 	for user space applications reside in a package that is not part of
419 a command line tool, numactl(8), exists that allows one to:
435 that require a node or set of nodes, the nodes are restricted to the set of
437 specified for the policy contains nodes that are not allowed by the cpuset and
450 cpuset information and requires that one know in what cpusets other task might