Searched refs:hugepage (Results 1 – 20 of 20) sorted by relevance
| /linux-6.1.9/tools/testing/selftests/vm/ |
| D | .gitignore | 2 hugepage-mmap
3 hugepage-mremap
4 hugepage-shm
5 hugepage-vmemmap
|
| D | run_vmtests.sh | 90 run_test ./hugepage-mmap
96 run_test ./hugepage-shm
102 run_test ./hugepage-mremap "$mnt"/huge_mremap
105 run_test ./hugepage-vmemmap
|
| D | Makefile | 32 TEST_GEN_FILES += hugepage-mmap
33 TEST_GEN_FILES += hugepage-mremap
34 TEST_GEN_FILES += hugepage-shm
35 TEST_GEN_FILES += hugepage-vmemmap
|
| /linux-6.1.9/Documentation/mm/ |
| D | transhuge.rst | 14 - "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-6.1.9/Documentation/arm64/ |
| D | hugetlbpage.rst | 20 mappings reduce the depth of page table walk needed to translate hugepage
35 The following hugepage sizes are supported -
|
| /linux-6.1.9/mm/ |
| D | hugetlb_cgroup.c | 38 return &h_cg->hugepage[idx]; in __hugetlb_cgroup_counter_from_cgroup()
208 page_counter_charge(&parent->hugepage[idx], nr_pages); in hugetlb_cgroup_move_parent()
210 counter = &h_cg->hugepage[idx]; in hugetlb_cgroup_move_parent()
496 page_counter_read(&h_cg->hugepage[idx]) * PAGE_SIZE); in hugetlb_cgroup_read_numa_stat()
526 counter = &h_cg->hugepage[MEMFILE_IDX(cft->private)]; in hugetlb_cgroup_read_u64()
561 counter = &h_cg->hugepage[idx]; in hugetlb_cgroup_read_u64_max()
650 counter = &h_cg->hugepage[MEMFILE_IDX(of_cft(of)->private)]; in hugetlb_cgroup_reset()
|
| D | Kconfig | 1054 # Some architectures require a special hugepage directory format that is
1055 # required to support multiple hugepage sizes. For example a4fe3ce76
1056 # "powerpc/mm: Allow more flexible layouts for hugepage pagetables"
1057 # introduced it on powerpc. This allows for a more flexible hugepage
|
| D | mempolicy.c | 2168 unsigned long addr, bool hugepage) in vma_alloc_folio() argument
2205 if (unlikely(IS_ENABLED(CONFIG_TRANSPARENT_HUGEPAGE) && hugepage)) { in vma_alloc_folio()
|
| /linux-6.1.9/Documentation/admin-guide/mm/ |
| D | transhuge.rst | 61 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
198 one 2M hugepage. Each may happen independently, or together, depending on
248 You can control hugepage allocation policy in tmpfs with mount option
270 There's also sysfs knob to control hugepage allocation policy for internal
419 memory region, the mmap region has to be hugepage naturally
425 You can use hugetlbfs on a kernel that has transparent hugepage
|
| D | hugetlbpage.rst | 68 is the default hugepage size (in kB).
148 It will allocate 1 2M hugepage on node0 and 2 2M hugepages on node1.
311 When adjusting the persistent hugepage count via ``nr_hugepages_mempolicy``, any
454 not hugepage aligned. For example, munmap(2) will fail if memory is backed by
455 a hugetlb page and the length is smaller than the hugepage size.
466 ``hugepage-shm``
467 see tools/testing/selftests/vm/hugepage-shm.c
469 ``hugepage-mmap``
470 see tools/testing/selftests/vm/hugepage-mmap.c
|
| D | userfaultfd.rst | 40 Vmas are not suitable for page- (or hugepage) granular fault tracking
|
| /linux-6.1.9/Documentation/ |
| D | dontdiff | 141 hugepage-mmap
142 hugepage-shm
|
| /linux-6.1.9/include/linux/ |
| D | gfp.h | 267 unsigned long addr, bool hugepage);
277 #define vma_alloc_folio(gfp, order, vma, addr, hugepage) \ argument
|
| D | hugetlb_cgroup.h | 50 struct page_counter hugepage[HUGE_MAX_HSTATE]; member
|
| /linux-6.1.9/Documentation/admin-guide/cgroup-v1/ |
| D | hugetlb.rst | 34 For a system supporting three hugepage sizes (64k, 32M and 1G), the control
|
| /linux-6.1.9/Documentation/trace/ |
| D | events-kmem.rst | 119 pageblock_size is usually the size of the default hugepage size.
|
| /linux-6.1.9/Documentation/translations/zh_CN/admin-guide/mm/damon/ |
| D | usage.rst | 211 - ``hugepage``: 为带有 ``MADV_HUGEPAGE`` 的区域调用 ``madvise()`` 。
|
| /linux-6.1.9/Documentation/admin-guide/sysctl/ |
| D | vm.rst | 560 Change the minimum size of the hugepage pool.
605 Change the size of the hugepage pool at run-time on a specific
614 Change the maximum size of the hugepage pool. The maximum is
|
| /linux-6.1.9/Documentation/admin-guide/mm/damon/ |
| D | usage.rst | 265 - ``hugepage``: Call ``madvise()`` for the region with ``MADV_HUGEPAGE``
|
| /linux-6.1.9/Documentation/filesystems/ |
| D | proc.rst | 504 "AnonHugePages" shows the ammount of memory backed by transparent hugepage.
921 A page block is typically the size of the default hugepage size, e.g. 2MB on
|