Lines Matching full:policies

15 Memory policies should not be confused with cpusets
18 memory may be allocated by a set of processes. Memory policies are a
20 both cpusets and policies are applied to a task, the restrictions of the cpuset
21 takes priority.  See :ref:`Memory Policies and cpusets <mem_pol_and_cpusets>`
27 Scope of Memory Policies
61 	In a multi-threaded task, task policies apply only to the thread
88 	VMA policies have a few complicating details:
100 	* VMA policies are shared between all tasks that share a
103 	  fork().  However, because VMA policies refer to a specific
105 	  space is discarded and recreated on exec*(), VMA policies
107 	  applications may use VMA policies.
123 	Conceptually, shared policies apply to "memory objects" mapped
125 	application installs shared policies the same way as VMA
126 	policies--using the mbind() system call specifying a range of
128 	VMA policies, which can be considered to be an attribute of a
129 	range of a task's address space, shared policies apply
143 	As mentioned above in :ref:`VMA policies <vma_policy>` section,
151 	The shared policy infrastructure supports different policies on subset
160 Components of Memory Policies
169 Internally, memory policies are implemented by a reference counted
290 	MPOL_PREFERRED policies that were created with an empty nodemask
331 	nodemasks to specify memory policies using this flag should
341 	MPOL_PREFERRED policies that were created with an empty nodemask
380    target task's task policy nor vma policies because we always acquire the
383    installing or replacing task or vma policies.  Thus, there is no possibility
392 4) Shared policies require special consideration.  One task can replace a
399    extra reference on shared policies in the same query/allocation paths
400    used for non-shared policies.  For this reason, shared policies are marked
402    for shared policies.
405    shared policies in a tree structure under spinlock, shared policies are
407    true for shared policies on shared memory regions shared by tasks running
502 Memory Policies and cpusets
505 Memory policies work within cpusets as described above.  For memory policies
515 The interaction of memory policies and cpusets can be problematic when tasks
519 memories are allowed in both cpusets may be used in the policies.  Obtaining