Lines Matching refs:routine

105 These operations result in a call to the routine hugetlb_reserve_pages()::
114 was specified, then this routine returns immediately as no reservations
152 reservations is known.  The routine hugetlb_acct_memory() is called to check
184 is performed within the routine alloc_huge_page()::
197 The helper routine vma_needs_reservation() is called to determine if a
200 information on what this routine does.
208 exists and can be used for the allocation, the routine dequeue_huge_page_vma()
209 is called.  This routine takes two arguments related to reservations:
240 The routine vma_commit_reservation() is then called to adjust the reserve
275 Huge page freeing is performed by the routine free_huge_page().  This routine
288 The routine first calls hugepage_subpool_put_pages() for the page.  If this
289 routine returns a value of 0 (which does not equal the value passed 1) it
374 a reservation map helper routine is called which calls one of these low level
416 The routine region_del() is called to remove regions from a reservation map.
440 situation, the routine hugetlb_fix_reserve_counts() is called to adjust the
471 This routine calls region_chg() for the specified page.  If no reservation
479 and region_add, this routine is to be called after a previous call to
491 and region_abort, this routine is to be called after a previous call to
499 This is a special wrapper routine to help facilitate reservation cleanup
500 on error paths.  It is only called from the routine restore_reserve_on_error().
501 This routine is used in conjunction with vma_needs_reservation in an attempt
535 The routine restore_reserve_on_error() attempts to handle this situation.  It
536 is fairly well documented.  The intention of this routine is to restore
541 The routine restore_reserve_on_error itself may encounter errors while