Lines Matching full:policies

17 Memory policies should not be confused with cpusets
20 memory may be allocated by a set of processes. Memory policies are a
22 both cpusets and policies are applied to a task, the restrictions of the cpuset
23 takes priority.  See :ref:`Memory Policies and cpusets <mem_pol_and_cpusets>`
29 Scope of Memory Policies
63 	In a multi-threaded task, task policies apply only to the thread
90 	VMA policies have a few complicating details:
102 	* VMA policies are shared between all tasks that share a
105 	  fork().  However, because VMA policies refer to a specific
107 	  space is discarded and recreated on exec*(), VMA policies
109 	  applications may use VMA policies.
125 	Conceptually, shared policies apply to "memory objects" mapped
127 	application installs shared policies the same way as VMA
128 	policies--using the mbind() system call specifying a range of
130 	VMA policies, which can be considered to be an attribute of a
131 	range of a task's address space, shared policies apply
145 	As mentioned above in :ref:`VMA policies <vma_policy>` section,
153 	The shared policy infrastructure supports different policies on subset
162 Components of Memory Policies
171 Internally, memory policies are implemented by a reference counted
283 	MPOL_PREFERRED policies that were created with an empty nodemask
324 	nodemasks to specify memory policies using this flag should
334 	MPOL_PREFERRED policies that were created with an empty nodemask
373    target task's task policy nor vma policies because we always acquire the
376    installing or replacing task or vma policies.  Thus, there is no possibility
385 4) Shared policies require special consideration.  One task can replace a
392    extra reference on shared policies in the same query/allocation paths
393    used for non-shared policies.  For this reason, shared policies are marked
395    for shared policies.
398    shared policies in a tree structure under spinlock, shared policies are
400    true for shared policies on shared memory regions shared by tasks running
481 Memory Policies and cpusets
484 Memory policies work within cpusets as described above.  For memory policies
494 The interaction of memory policies and cpusets can be problematic when tasks
498 memories are allowed in both cpusets may be used in the policies.  Obtaining