Lines Matching refs:policies

11 Memory policies should not be confused with cpusets
14 memory may be allocated by a set of processes. Memory policies are a
16 both cpusets and policies are applied to a task, the restrictions of the cpuset
50 	In a multi-threaded task, task policies apply only to the thread
72     VMA policies have a few complicating details:
83 	VMA policies are shared between all tasks that share a virtual address
85 	they are inherited across fork().  However, because VMA policies refer
87 	space is discarded and recreated on exec*(), VMA policies are NOT
89 	use VMA policies.
102     Shared Policy:  Conceptually, shared policies apply to "memory objects"
104     application installs a shared policies the same way as VMA policies--using
106     the shared object.  However, unlike VMA policies, which can be considered
107     to be an attribute of a range of a task's address space, shared policies
121 	As mentioned above [re: VMA policies], allocations of page cache
128 	The shared policy infrastructure supports different policies on subset
145    Internally, memory policies are implemented by a reference counted
242 	    MPOL_PREFERRED policies that were created with an empty nodemask
282 	    nodemasks to specify memory policies using this flag should
292 	    MPOL_PREFERRED policies that were created with an empty nodemask
330    target task's task policy nor vma policies because we always acquire the
333    installing or replacing task or vma policies.  Thus, there is no possibility
342 4) Shared policies require special consideration.  One task can replace a
349    extra reference on shared policies in the same query/allocation paths
350    used for non-shared policies.  For this reason, shared policies are marked
352    for shared policies.
355    shared policies in a tree structure under spinlock, shared policies are
357    true for shared policies on shared memory regions shared by tasks running
434 Memory policies work within cpusets as described above.  For memory policies
444 The interaction of memory policies and cpusets can be problematic when tasks
448 memories are allowed in both cpusets may be used in the policies.  Obtaining