Lines Matching full:routine

103 These operations result in a call to the routine hugetlb_reserve_pages()::
112 was specified, then this routine returns immediately as no reservations
150 reservations is known.  The routine hugetlb_acct_memory() is called to check
182 is performed within the routine alloc_hugetlb_folio()::
195 The helper routine vma_needs_reservation() is called to determine if a
198 information on what this routine does.
206 exists and can be used for the allocation, the routine dequeue_huge_page_vma()
207 is called.  This routine takes two arguments related to reservations:
239 The routine vma_commit_reservation() is then called to adjust the reserve
287 The routine first calls hugepage_subpool_put_pages() for the page.  If this
288 routine returns a value of 0 (which does not equal the value passed 1) it
373 a reservation map helper routine is called which calls one of these low level
415 The routine region_del() is called to remove regions from a reservation map.
439 situation, the routine hugetlb_fix_reserve_counts() is called to adjust the
470 This routine calls region_chg() for the specified page.  If no reservation
478 and region_add, this routine is to be called after a previous call to
490 and region_abort, this routine is to be called after a previous call to
498 This is a special wrapper routine to help facilitate reservation cleanup
499 on error paths.  It is only called from the routine restore_reserve_on_error().
500 This routine is used in conjunction with vma_needs_reservation in an attempt
534 The routine restore_reserve_on_error() attempts to handle this situation.  It
535 is fairly well documented.  The intention of this routine is to restore
540 The routine restore_reserve_on_error itself may encounter errors while