Lines Matching full:shared

100 	* VMA policies are shared between all tasks that share a
122 Shared Policy
123 	Conceptually, shared policies apply to "memory objects" mapped
124 	shared into one or more tasks' distinct address spaces.  An
125 	application installs shared policies the same way as VMA
127 	virtual addresses that map the shared object.  However, unlike
129 	range of a task's address space, shared policies apply
130 	directly to the shared object.  Thus, all tasks that attach to
132 	shared object, by any task, will obey the shared policy.
134 	As of 2.6.22, only shared memory segments, created by shmget() or
135 	mmap(MAP_ANONYMOUS|MAP_SHARED), support shared policy.  When shared
139 	shmem segments were never "hooked up" to the shared policy support.
141 	for shared policy has not been completed.
146 	address range backed by the shared file mapping.  Rather,
147 	shared page cache pages, including pages backing private
151 	The shared policy infrastructure supports different policies on subset
152 	ranges of the shared object.  However, Linux still splits the VMA of
154 	Thus, different tasks that attach to a shared memory segment can have
155 	different VMA configurations mapping that one shared object.  This
157 	a shared memory region, when one task has installed shared policy on
226 	For allocation of anonymous pages and shared memory pages,
392 4) Shared policies require special consideration.  One task can replace a
393    shared memory policy while another task, with a distinct mmap_lock, is
395    potential race, the shared policy infrastructure adds an extra reference
396    to the shared policy during lookup while holding a spin lock on the shared
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
409    falling back to task or system default policy for shared memory regions,
410    or by prefaulting the entire shared memory region into memory and locking
420 some shared object mapped into the calling task's address space.
457 Install VMA/Shared Policy for a Range of Task's Address Space::
493 + set the shared policy for a shared memory segment via mbind(2)
516 in two cpusets share access to a memory region, such as shared memory segments
518 any of the tasks install shared policy on the region, only nodes whose
522 be attaching to the shared region.  Furthermore, if the cpusets' allowed