Searched refs:hugepage (Results 1 – 18 of 18) sorted by relevance
| /Linux-v5.4/mm/ |
| D | hugetlb_cgroup.c | 27 struct page_counter hugepage[HUGE_MAX_HSTATE]; member
64 if (page_counter_read(&h_cg->hugepage[idx])) in hugetlb_cgroup_have_usage()
76 struct page_counter *counter = &h_cgroup->hugepage[idx]; in hugetlb_cgroup_init()
82 parent = &parent_h_cgroup->hugepage[idx]; in hugetlb_cgroup_init()
146 page_counter_charge(&parent->hugepage[idx], nr_pages); in hugetlb_cgroup_move_parent()
148 counter = &h_cg->hugepage[idx]; in hugetlb_cgroup_move_parent()
205 if (!page_counter_try_charge(&h_cg->hugepage[idx], nr_pages, &counter)) in hugetlb_cgroup_charge_cgroup()
240 page_counter_uncharge(&h_cg->hugepage[idx], nr_pages); in hugetlb_cgroup_uncharge_page()
253 page_counter_uncharge(&h_cg->hugepage[idx], nr_pages); in hugetlb_cgroup_uncharge_cgroup()
270 counter = &h_cg->hugepage[MEMFILE_IDX(cft->private)]; in hugetlb_cgroup_read_u64()
[all …]
|
| D | Kconfig | 730 # Some architectures require a special hugepage directory format that is
731 # required to support multiple hugepage sizes. For example a4fe3ce76
732 # "powerpc/mm: Allow more flexible layouts for hugepage pagetables"
733 # introduced it on powerpc. This allows for a more flexible hugepage
|
| D | mempolicy.c | 2099 unsigned long addr, int node, bool hugepage) in alloc_pages_vma() argument
2117 if (unlikely(IS_ENABLED(CONFIG_TRANSPARENT_HUGEPAGE) && hugepage)) { in alloc_pages_vma()
|
| /Linux-v5.4/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.4/tools/testing/selftests/vm/ |
| D | .gitignore | 1 hugepage-mmap
2 hugepage-shm
|
| D | Makefile | 8 TEST_GEN_FILES += hugepage-mmap
9 TEST_GEN_FILES += hugepage-shm
|
| D | run_vmtests | 67 ./hugepage-mmap
82 ./hugepage-shm
|
| /Linux-v5.4/Documentation/arm64/ |
| D | hugetlbpage.rst | 18 mappings reduce the depth of page table walk needed to translate hugepage
33 The following hugepage sizes are supported -
|
| /Linux-v5.4/Documentation/ |
| D | dontdiff | 140 hugepage-mmap
141 hugepage-shm
|
| /Linux-v5.4/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
234 You can control hugepage allocation policy in tmpfs with mount option
256 There's also sysfs knob to control hugepage allocation policy for internal
408 memory region, the mmap region has to be hugepage naturally
414 You can use hugetlbfs on a kernel that has transparent hugepage
|
| D | hugetlbpage.rst | 64 is the default hugepage size (in Kb).
218 When adjusting the persistent hugepage count via ``nr_hugepages_mempolicy``, any
361 not hugepage aligned. For example, munmap(2) will fail if memory is backed by
362 a hugetlb page and the length is smaller than the hugepage size.
373 ``hugepage-shm``
374 see tools/testing/selftests/vm/hugepage-shm.c
376 ``hugepage-mmap``
377 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.4/Documentation/admin-guide/cgroup-v1/ |
| D | hugetlb.rst | 36 For a system supporting three hugepage sizes (64k, 32M and 1G), the control
|
| /Linux-v5.4/include/linux/ |
| D | gfp.h | 536 int node, bool hugepage);
|
| /Linux-v5.4/Documentation/trace/ |
| D | events-kmem.rst | 119 pageblock_size is usually the size of the default hugepage size.
|
| /Linux-v5.4/Documentation/admin-guide/sysctl/ |
| D | vm.rst | 546 Change the minimum size of the hugepage pool.
554 Change the size of the hugepage pool at run-time on a specific
563 Change the maximum size of the hugepage pool. The maximum is
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | proc.txt | 477 "AnonHugePages" shows the ammount of memory backed by transparent hugepage.
856 A page block is typically the size of the default hugepage size e.g. 2MB on
|
