Lines Matching refs:VMA
76 VMA Policy
77 A "VMA" or "Virtual Memory Area" refers to a range of a task's
81 below, for an overview of the mbind() system call used to set a VMA
84 A VMA policy will govern the allocation of pages that back
86 address space that don't have an explicit VMA policy will fall
90 VMA policies have a few complicating details:
92 * VMA policy applies ONLY to anonymous pages. These include
95 mmap()ed with the MAP_ANONYMOUS flag. If a VMA policy is
98 MAP_PRIVATE flag, the VMA policy will only be applied when
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.
111 * A task may install a new VMA policy on a sub-range of a
116 * By default, VMA policy applies only to pages allocated after
118 VMA range remain where they were allocated based on the
127 application installs shared policies the same way as VMA
130 VMA policies, which can be considered to be an attribute of a
145 As mentioned above in :ref:`VMA policies <vma_policy>` section,
147 with MAP_SHARED ignore any VMA policy installed on the virtual
154 ranges of the shared object. However, Linux still splits the VMA of
157 different VMA configurations mapping that one shared object. This
231 segment [VMA] containing the address modulo the number of
252 the user should not be remapped if the task or VMA's set of allowed
281 by the user will be mapped relative to the set of the task or VMA's
301 relative to task or VMA's set of allowed nodes.
443 Install VMA/Shared Policy for a Range of Task's Address Space::
450 VMA policy for the range of the calling task's address space specified