Lines Matching full:shared

102 	* VMA policies are shared between all tasks that share a
124 Shared Policy
125 	Conceptually, shared policies apply to "memory objects" mapped
126 	shared into one or more tasks' distinct address spaces.  An
127 	application installs shared policies the same way as VMA
129 	virtual addresses that map the shared object.  However, unlike
131 	range of a task's address space, shared policies apply
132 	directly to the shared object.  Thus, all tasks that attach to
134 	shared object, by any task, will obey the shared policy.
136 	As of 2.6.22, only shared memory segments, created by shmget() or
137 	mmap(MAP_ANONYMOUS|MAP_SHARED), support shared policy.  When shared
141 	shmem segments were never "hooked up" to the shared policy support.
143 	for shared policy has not been completed.
148 	address range backed by the shared file mapping.  Rather,
149 	shared page cache pages, including pages backing private
153 	The shared policy infrastructure supports different policies on subset
154 	ranges of the shared object.  However, Linux still splits the VMA of
156 	Thus, different tasks that attach to a shared memory segment can have
157 	different VMA configurations mapping that one shared object.  This
159 	a shared memory region, when one task has installed shared policy on
228 	For allocation of anonymous pages and shared memory pages,
378 4) Shared policies require special consideration.  One task can replace a
379    shared memory policy while another task, with a distinct mmap_lock, is
381    potential race, the shared policy infrastructure adds an extra reference
382    to the shared policy during lookup while holding a spin lock on the shared
385    extra reference on shared policies in the same query/allocation paths
386    used for non-shared policies.  For this reason, shared policies are marked
388    for shared policies.
391    shared policies in a tree structure under spinlock, shared policies are
393    true for shared policies on shared memory regions shared by tasks running
395    falling back to task or system default policy for shared memory regions,
396    or by prefaulting the entire shared memory region into memory and locking
406 some shared object mapped into the calling task's address space.
443 Install VMA/Shared Policy for a Range of Task's Address Space::
465 + set the shared policy for a shared memory segment via mbind(2)
488 in two cpusets share access to a memory region, such as shared memory segments
490 any of the tasks install shared policy on the region, only nodes whose
494 be attaching to the shared region.  Furthermore, if the cpusets' allowed