Searched refs:hugepage (Results 1 – 19 of 19) sorted by relevance
| /Linux-v5.10/Documentation/vm/ |
| 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.
66 pmd_offset. It's trivial to make the code transparent hugepage aware
71 hugepage aware.
73 If you're not walking pagetables but you run into a physical hugepage
76 it tries to swapout the hugepage for example. split_huge_page() can fail
[all …]
|
| D | hwpoison.rst | 183 - Right now hugepage support is missing.
|
| /Linux-v5.10/tools/testing/selftests/vm/ |
| D | .gitignore | 2 hugepage-mmap
3 hugepage-shm
|
| D | run_vmtests | 75 ./hugepage-mmap
90 ./hugepage-shm
|
| D | Makefile | 28 TEST_GEN_FILES += hugepage-mmap
29 TEST_GEN_FILES += hugepage-shm
|
| /Linux-v5.10/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-v5.10/mm/ |
| D | hugetlb_cgroup.c | 31 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()
425 counter = &h_cg->hugepage[MEMFILE_IDX(cft->private)]; in hugetlb_cgroup_read_u64()
460 counter = &h_cg->hugepage[idx]; in hugetlb_cgroup_read_u64_max()
549 counter = &h_cg->hugepage[MEMFILE_IDX(of_cft(of)->private)]; in hugetlb_cgroup_reset()
|
| D | Kconfig | 850 # Some architectures require a special hugepage directory format that is
851 # required to support multiple hugepage sizes. For example a4fe3ce76
852 # "powerpc/mm: Allow more flexible layouts for hugepage pagetables"
853 # introduced it on powerpc. This allows for a more flexible hugepage
|
| D | mempolicy.c | 2174 unsigned long addr, int node, bool hugepage) in alloc_pages_vma() argument
2192 if (unlikely(IS_ENABLED(CONFIG_TRANSPARENT_HUGEPAGE) && hugepage)) { in alloc_pages_vma()
|
| /Linux-v5.10/Documentation/ |
| D | dontdiff | 141 hugepage-mmap
142 hugepage-shm
|
| /Linux-v5.10/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
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
428 memory region, the mmap region has to be hugepage naturally
434 You can use hugetlbfs on a kernel that has transparent hugepage
|
| D | hugetlbpage.rst | 64 is the default hugepage size (in Kb).
264 When adjusting the persistent hugepage count via ``nr_hugepages_mempolicy``, any
407 not hugepage aligned. For example, munmap(2) will fail if memory is backed by
408 a hugetlb page and the length is smaller than the hugepage size.
419 ``hugepage-shm``
420 see tools/testing/selftests/vm/hugepage-shm.c
422 ``hugepage-mmap``
423 see tools/testing/selftests/vm/hugepage-mmap.c
|
| D | userfaultfd.rst | 38 Vmas are not suitable for page- (or hugepage) granular fault tracking
|
| /Linux-v5.10/include/linux/ |
| D | hugetlb_cgroup.h | 44 struct page_counter hugepage[HUGE_MAX_HSTATE]; member
|
| D | gfp.h | 551 int node, bool hugepage);
|
| /Linux-v5.10/Documentation/trace/ |
| D | events-kmem.rst | 119 pageblock_size is usually the size of the default hugepage size.
|
| /Linux-v5.10/Documentation/admin-guide/cgroup-v1/ |
| D | hugetlb.rst | 33 For a system supporting three hugepage sizes (64k, 32M and 1G), the control
|
| /Linux-v5.10/Documentation/admin-guide/sysctl/ |
| D | vm.rst | 566 Change the minimum size of the hugepage pool.
574 Change the size of the hugepage pool at run-time on a specific
583 Change the maximum size of the hugepage pool. The maximum is
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | proc.rst | 497 "AnonHugePages" shows the ammount of memory backed by transparent hugepage.
900 A page block is typically the size of the default hugepage size, e.g. 2MB on
|
