Lines Matching refs:it

12 Currently it only works for anonymous memory mappings but in the
13 future it can expand over the pagecache layer starting with tmpfs.
16 factors. The first factor is almost completely irrelevant and it's not
17 of significant interest because it'll also have the downside of
53 - it doesn't require memory reservation and in turn it uses hugepages
56   is not specific to transparent hugepage support and it's a generic
61   regions but it'd be ideal to move it to tmpfs and the pagecache
71 advantage of it.
82 large region but only touch 1 byte of it, in that case a 2M page might
83 be allocated instead of a 4k page for no good. This is why it's
112 guaranteed, but it may be more likely in case the allocation is for a
120 It's possible to disable huge zero page by writing 0 or enable it
127 transparent_hugepage/enabled is set to "always" or "madvise, and it'll
128 be automatically shutdown if it's set to "never".
131 invoke defrag algorithms synchronously during the page faults, it
132 should be worth invoking defrag at least in khugepaged. However it's
171 ignore it.
191 identify what applications are using transparent huge pages, it is
194 reading it frequently will incur overhead.
203 thp_collapse_alloc is incremented by khugepaged when it has found
220 	dropped due race with other allocation. Note, it doesn't count
241 	this value is increasing rapidly, it implies that the system
266 for the head page and not the tail page), it should be updated to jump
269 under it, see the futex code to see an example of that, hugetlbfs also
279 follow_page, so that it will split the hugepages before returning
281 follow_page because it's not hugepage aware and in fact it can't work
282 at all on hugetlbfs (but it instead works fine on transparent
284 hugepages being returned (as it's not only checking the pfn of the
285 page and pinning it during the copy but it pretends to migrate the
314 but you can't handle it natively in your code, you can split it by
316 it tries to swapout the hugepage for example.
350 case pmd_trans_splitting returns true, it means split_huge_page is
352 returns true it's enough to drop the page_table_lock and call
379 too, to know when we can free the compound page in case it's never
382 page (and only on a tail page) it will find its respective head page,
383 and then it will decrease the head page refcount in addition to the