Lines Matching full:mapping

17 huge pages to cover the mapping, the mmap() would fail.  This was first
19 were enough free huge pages to cover the mapping.  Like most things in the
22 available for page faults in that mapping.  The description below attempts to
52 	There is one reserve map for each huge page mapping in the system.
54 	the mapping.  A region is described as::
63 	indices into the mapping.  Depending on the type of mapping, a
71 		associated with the mapping.
73 		Indicates task originally mapping this range (and creating
85 A huge page mapping or segment is either private or shared.  If private,
93   time the mapping (mmap(MAP_PRIVATE)) is created.
104 created (shmget(SHM_HUGETLB)) or a mapping is created via mmap(MAP_HUGETLB).
117 The arguments 'from' and 'to' are huge page indices into the mapping or
119 the length of the segment/mapping.  For mmap(), the offset argument could
140 are needed for the current mapping/segment.  For private mappings, this is
146 The mapping may be associated with a subpool.  If so, the subpool is consulted
147 to ensure there is sufficient space for the mapping.  It is possible that the
148 subpool has set aside reservations that can be used for the mapping.  See the
167 was adjusted, then the reservation map associated with the mapping is
168 modified to reflect the reservations.  In the case of a shared mapping, a
174 reservation map associated with the mapping will be modified as required to
183 are allocated and instantiated in the corresponding mapping.  The allocation
198 reservation exists for the address within the mapping(vma).  See the section
204 mapping the subpool is consulted to determine if it contains reservations.
245 was no reservation in a shared mapping or this was a private mapping a new
252 mapping.  In such cases, the reservation count and subpool free page count
265 of the allocating task.  Before this, pages in a shared mapping are added
267 reverse mapping.  In both cases, the PagePrivate flag is cleared.  Therefore,
348 When the private mapping was originally created, the owner of the mapping
350 map of the owner.  Since the owner created the mapping, the owner owns all
351 the reservations associated with the mapping.  Therefore, when a write fault
364 mapping/reservation will behave as expected.
444 region_count() is called when unmapping a private huge page mapping.  In
449 Since the mapping is going away, the subpool and global reservation counts
460 they pass in the associated VMA.  From the VMA, the type of mapping (private
574 	 * The change of semantics for shared hugetlb mapping with cpuset is