Lines Matching refs:hugepage

39   hugepage knowledge fall back to breaking a transparent hugepage and
43 - if a hugepage allocation fails because of memory fragmentation,
56   is not specific to transparent hugepage support and it's a generic
67 entities). It doesn't require reservation to prevent hugepage
77 lived page allocations even for hugepage unaware applications that
149 and how many milliseconds to wait in khugepaged if there's an hugepage
269 get_user_pages and follow_page if run on a hugepage, will return the
285 hugepage backed mappings.
291 follow_page because it's not hugepage aware and in fact it can't work
301 memory region, the mmap region has to be hugepage naturally
306 You can use hugetlbfs on a kernel that has transparent hugepage
316 pmd_offset. It's trivial to make the code transparent hugepage aware
321 hugepage aware.
323 If you're not walking pagetables but you run into a physical hugepage
326 it tries to swapout the hugepage for example.
328 Example to make mremap.c transparent hugepage aware with a one liner
342 == Locking in hugepage aware code ==
344 We want as much code as possible hugepage aware, as calling
366 process the huge pmd and the hugepage natively. Once finished you can
376 hugepage), requires the refcount to be accounted on the tail pages and