Documentation/vm/hugetlbfs_reserv.rst

64 	region in the reserv_map may indicate reservations exist for the
65 	range, or reservations do not exist.
70 		Indicates this task is the owner of the reservations
114 was specified, then this routine returns immediately as no reservations
124 in which reservations are represented in the reservation map.
127   exists or did exist for the corresponding page.  As reservations are
130   a reservation exists for the corresponding page.  As reservations are
132   reservation map can also be used to determine which reservations have
137 to indicate this VMA owns the reservations.
139 The reservation map is consulted to determine how many huge page reservations
142 some reservations may already exist within the range (to - from).  See the
148 subpool has set aside reservations that can be used for the mapping.  See the
152 reservations is known.  The routine hugetlb_acct_memory() is called to check
153 for and take the requested number of reservations.  hugetlb_acct_memory()
168 modified to reflect the reservations.  In the case of a shared mapping, a
175 ensure reservations exist for the range 'from' - 'to'.
182 Reservations are consumed when huge pages associated with the reservations
204 mapping the subpool is consulted to determine if it contains reservations.
205 If the subpool contains reservations, one can be used for this allocation.
209 is called.  This routine takes two arguments related to reservations:
232 the scope reservations.  Even if a surplus page is allocated, the same
317 accounting, and track any reservations associated with the subpool.
351 the reservations associated with the mapping.  Therefore, when a write fault
447 reservation map we know how many reservations were consumed and how many are
450 are decremented by the number of outstanding reservations.
458 These routines are only interested with reservations for a specific huge
557 to manage Linux code.  The concept of reservations was added some time later.
558 When reservations were added, no attempt was made to take memory policy
560 comment in hugetlb_acct_memory sums up the interaction between reservations
581 Huge page reservations were added to prevent unexpected page allocation
585 number of global reservations.