Lines Matching refs:by

14 memory may be allocated by a set of processes. Memory policies are a
28     by one of the more specific policy scopes discussed below.  When the
36     for a specific task, this policy controls all page allocations made by or
37     on behalf of the task that aren't controlled by a more specific scope.
39     would have been controlled by the task policy "fall back" to the System
52 	subsequently created by that thread.  Any sibling threads existing
57 	installed.  Any pages already faulted in by the task when the task
110     by any task, will obey the shared policy.
112 	As of 2.6.22, only shared memory segments, created by shmget() or
123 	policy installed on the virtual address range backed by the shared
125 	private mappings that have not yet been written by the task, follow
133 	can be seen by examining the /proc/<pid>/numa_maps of tasks sharing
145    Internally, memory policies are implemented by a reference counted
168 	set of nodes specified by the policy.  Memory will be allocated from
176 	provided by the platform firmware.
186 	    always preferred by passing an empty nodemask with this mode.
197 	    Interleave mode indexes the set of nodes specified by the policy
200 	    by the policy.  It then attempts to allocate a page, starting at
201 	    the selected node, as if the node had been specified by a Preferred
202 	    policy or had been selected by a local allocation.  That is,
206 	    of nodes specified by the policy using a node counter maintained
209 	    spread the pages out over the nodes specified by the policy based
217 	MPOL_F_STATIC_NODES:  This flag specifies that the nodemask passed by
228 	    nodes allowed by the task's cpuset, then the memory policy is
246 	by the user will be mapped relative to the set of the task or VMA's
265 	    allowed nodes.  The nodemask passed by the user represents nodes
287 	    set of memory nodes allowed by the task's cpuset, as that may
304 to '1', representing the reference held by the task that is installing the
313 1) querying of the policy, either by the task itself [using the get_mempolicy()
314    API discussed below] or by another task using the /proc/<pid>/numa_maps
321    BIND policy nodemask is used, by reference, to filter ineligible nodes.
357    true for shared policies on shared memory regions shared by tasks running
358    on different NUMA nodes.  This extra overhead can be avoided by always
360    or by prefaulting the entire shared memory region into memory and locking
381 	specified by the 'mode' argument and the set of nodes defined
382 	by 'nmask'.  'nmask' points to a bit mask of node ids containing
383 	at least 'maxnode' ids.  Optional mode flags may be passed by
409 	mbind() installs the policy specified by (mode, nmask, maxnodes) as
411 	specified by the 'start' and 'len' arguments.  Additional actions
436 nodes whose memories are allowed by the cpuset constraints.  If the nodemask
437 specified for the policy contains nodes that are not allowed by the cpuset and
446 created by shmget() of mmap() with the MAP_ANONYMOUS and MAP_SHARED flags, and