Home
last modified time | relevance | path

Searched refs:huge (Results 1 – 4 of 4) sorted by relevance

/mm/
Dshmem.c125 int huge; member
506 static const char *shmem_format_huge(int huge) in shmem_format_huge() argument
508 switch (huge) { in shmem_format_huge()
670 (shmem_huge == SHMEM_HUGE_FORCE || sbinfo->huge) && in is_huge_enabled()
1590 pgoff_t index, bool huge) in shmem_alloc_and_acct_page() argument
1598 huge = false; in shmem_alloc_and_acct_page()
1599 nr = huge ? HPAGE_PMD_NR : 1; in shmem_alloc_and_acct_page()
1604 if (huge) in shmem_alloc_and_acct_page()
1894 switch (sbinfo->huge) { in shmem_getpage_gfp()
2205 if (SHMEM_SB(sb)->huge == SHMEM_HUGE_NEVER) in shmem_get_unmapped_area()
[all …]
Dmemory-failure.c1784 bool huge = PageHuge(page); in __soft_offline_page() local
1829 bool release = !huge; in __soft_offline_page()
1831 if (!page_handle_poison(page, huge, release)) in __soft_offline_page()
1838 pfn, msg_page[huge], ret, page->flags, &page->flags); in __soft_offline_page()
1844 pfn, msg_page[huge], page_count(page), page->flags, &page->flags); in __soft_offline_page()
DKconfig223 with the reduced number of transparent huge pages that could be used
267 to the processors accessing. The second is when allocating huge
268 pages as migration can relocate pages to satisfy a huge page
394 Transparent Hugepages allows the kernel to use huge pages and
395 huge tlb transparently to the applications whenever possible.
434 Swap transparent huge pages in one piece, without splitting.
435 XXX: For now, swap cluster backing transparent huge page
Dfilemap.c841 int huge = PageHuge(page); in __add_to_page_cache_locked() local
853 if (!huge) { in __add_to_page_cache_locked()
898 if (!huge) in __add_to_page_cache_locked()