Home
last modified time | relevance | path

Searched refs:hugepage (Results 1 – 18 of 18) sorted by relevance

/Linux-v5.15/Documentation/vm/
Dtranshuge.rst14 - "graceful fallback": mm components which don't have transparent hugepage
16 if necessary, split a transparent hugepage. Therefore these components
19 - if a hugepage allocation fails because of memory fragmentation,
32 is not specific to transparent hugepage support and it's a generic
39 get_user_pages and follow_page if run on a hugepage, will return the
54 hugepage backed mappings.
61 pmd_offset. It's trivial to make the code transparent hugepage aware
66 hugepage aware.
68 If you're not walking pagetables but you run into a physical hugepage
71 it tries to swapout the hugepage for example. split_huge_page() can fail
[all …]
/Linux-v5.15/tools/testing/selftests/vm/
D.gitignore2 hugepage-mmap
3 hugepage-shm
Drun_vmtests.sh75 ./hugepage-mmap
90 ./hugepage-shm
DMakefile31 TEST_GEN_FILES += hugepage-mmap
32 TEST_GEN_FILES += hugepage-shm
/Linux-v5.15/mm/
Dhugetlb_cgroup.c31 container_of(counter, struct hugetlb_cgroup, hugepage[idx])
41 return &h_cg->hugepage[idx]; in __hugetlb_cgroup_counter_from_cgroup()
182 page_counter_charge(&parent->hugepage[idx], nr_pages); in hugetlb_cgroup_move_parent()
184 counter = &h_cg->hugepage[idx]; in hugetlb_cgroup_move_parent()
431 counter = &h_cg->hugepage[MEMFILE_IDX(cft->private)]; in hugetlb_cgroup_read_u64()
466 counter = &h_cg->hugepage[idx]; in hugetlb_cgroup_read_u64_max()
555 counter = &h_cg->hugepage[MEMFILE_IDX(of_cft(of)->private)]; in hugetlb_cgroup_reset()
DKconfig875 # Some architectures require a special hugepage directory format that is
876 # required to support multiple hugepage sizes. For example a4fe3ce76
877 # "powerpc/mm: Allow more flexible layouts for hugepage pagetables"
878 # introduced it on powerpc. This allows for a more flexible hugepage
Dmempolicy.c2086 unsigned long addr, int node, bool hugepage) in alloc_pages_vma() argument
2110 if (unlikely(IS_ENABLED(CONFIG_TRANSPARENT_HUGEPAGE) && hugepage)) { in alloc_pages_vma()
/Linux-v5.15/Documentation/arm64/
Dhugetlbpage.rst20 mappings reduce the depth of page table walk needed to translate hugepage
35 The following hugepage sizes are supported -
/Linux-v5.15/Documentation/
Ddontdiff141 hugepage-mmap
142 hugepage-shm
/Linux-v5.15/Documentation/admin-guide/mm/
Dtranshuge.rst61 entities). It doesn't require reservation to prevent hugepage
71 lived page allocations even for hugepage unaware applications that
159 library) may want to know the size (in bytes) of a transparent hugepage::
189 and how many milliseconds to wait in khugepaged if there's an hugepage
241 You can control hugepage allocation policy in tmpfs with mount option
263 There's also sysfs knob to control hugepage allocation policy for internal
413 memory region, the mmap region has to be hugepage naturally
419 You can use hugetlbfs on a kernel that has transparent hugepage
Dhugetlbpage.rst68 is the default hugepage size (in Kb).
275 When adjusting the persistent hugepage count via ``nr_hugepages_mempolicy``, any
418 not hugepage aligned. For example, munmap(2) will fail if memory is backed by
419 a hugetlb page and the length is smaller than the hugepage size.
430 ``hugepage-shm``
431 see tools/testing/selftests/vm/hugepage-shm.c
433 ``hugepage-mmap``
434 see tools/testing/selftests/vm/hugepage-mmap.c
Duserfaultfd.rst38 Vmas are not suitable for page- (or hugepage) granular fault tracking
/Linux-v5.15/include/linux/
Dhugetlb_cgroup.h45 struct page_counter hugepage[HUGE_MAX_HSTATE]; member
Dgfp.h591 int node, bool hugepage);
/Linux-v5.15/Documentation/trace/
Devents-kmem.rst119 pageblock_size is usually the size of the default hugepage size.
/Linux-v5.15/Documentation/admin-guide/cgroup-v1/
Dhugetlb.rst33 For a system supporting three hugepage sizes (64k, 32M and 1G), the control
/Linux-v5.15/Documentation/admin-guide/sysctl/
Dvm.rst559 Change the minimum size of the hugepage pool.
567 Change the size of the hugepage pool at run-time on a specific
576 Change the maximum size of the hugepage pool. The maximum is
/Linux-v5.15/Documentation/filesystems/
Dproc.rst499 "AnonHugePages" shows the ammount of memory backed by transparent hugepage.
914 A page block is typically the size of the default hugepage size, e.g. 2MB on