Lines Matching full:are
8 Huge pages as described at Documentation/admin-guide/mm/hugetlbpage.rst are
9 typically preallocated for application use. These huge pages are instantiated
11 are to be used. If no huge page exists at page fault time, the task is sent
26 This description is primarily targeted at kernel developers who are modifying
35 huge pages are only available to the task which reserved them.
60 The 'from' and 'to' fields of the file region structure are huge page
65 These are stored in the bottom bits of the reservation map pointer.
87 of mappings. Location differences are:
93 inode->i_mapping->private_data. Since shared mappings are always backed
101 Reservations are created when a huge page backed shared memory segment is
113 are desired.
115 The arguments 'from' and 'to' are huge page indices into the mapping or
122 in which reservations are represented in the reservation map.
125 exists or did exist for the corresponding page. As reservations are
128 a reservation exists for the corresponding page. As reservations are
129 consumed, entries are added to the reservation map. Therefore, the
138 are needed for the current mapping/segment. For private mappings, this is
154 are enough free huge pages to accommodate the reservation. If there are,
168 mappings, no modifications are made to the reservation map as lack of an
180 Reservations are consumed when huge pages associated with the reservations
181 are allocated and instantiated in the corresponding mapping. The allocation
193 page are being allocated.
211 - chg, even though this argument is of type long only the values 0 or 1 are
217 The free lists associated with the memory policy of the VMA are searched for
220 associated with the page, the following adjustments are made::
254 a race is detected, the subpool and global reserve counts are adjusted to
264 of the allocating task. Before this, pages in a shared mapping are added
265 to the page cache and pages in private mappings are added to an anonymous
274 Huge pages are freed by free_huge_folio(). It is only passed a pointer
285 for information on how these are set).
289 indicates reserves are associated with the subpool, and this newly free page
309 min_size are reserved for use by the filesystem. This number is tracked in
314 The routines hugepage_subpool_get/put_pages() are called when pages are
317 hugepage_subpool_get/put_pages are passed the number of huge pages by which
322 However, if reserves are associated with the subpool a return value less
344 COW, it is possible that no free huge pages are free and the allocation
371 The following low level routines are used to make modifications to a
372 reservation map. Typically, these routines are not called directly. Rather,
374 routines. These low level routines are fairly well documented in the source
375 code (mm/hugetlb.c). These routines are::
385 many pages in the specified range [f, t) are NOT currently represented.
388 there are enough huge pages for the operation to succeed.
398 are guaranteed to succeed after a prior call to region_chg() for the same
404 which are NOT currently represented in the map. This number is returned to
427 are removed from the middle of the file one at a time. As the pages are
446 reservation map we know how many reservations were consumed and how many are
449 are decremented by the number of outstanding reservations.
457 These routines are only interested with reservations for a specific huge
515 map modifications are performed in two steps. First vma_needs_reservation
518 Global and subpool reservation counts are adjusted based on success or failure
524 However, there are several instances where errors are encountered after a huge
558 into account. While cpusets are not exactly the same as memory policy, this
583 available on the required nodes. This is true even if there are a sufficient
589 The most complete set of hugetlb tests are in the libhugetlbfs repository.