Searched refs:hugepage (Results 1 – 22 of 22) sorted by relevance
| /linux-6.12.1/tools/testing/selftests/mm/ |
| D | .gitignore | 3 hugepage-mmap
4 hugepage-mremap
5 hugepage-shm
6 hugepage-vmemmap
|
| D | Makefile | 47 TEST_GEN_FILES += hugepage-mmap
48 TEST_GEN_FILES += hugepage-mremap
49 TEST_GEN_FILES += hugepage-shm
50 TEST_GEN_FILES += hugepage-vmemmap
|
| D | run_vmtests.sh | 254 CATEGORY="hugetlb" run_test ./hugepage-mmap
260 CATEGORY="hugetlb" run_test ./hugepage-shm
265 CATEGORY="hugetlb" run_test ./hugepage-mremap
266 CATEGORY="hugetlb" run_test ./hugepage-vmemmap
|
| /linux-6.12.1/Documentation/mm/ |
| D | transhuge.rst | 12 - "graceful fallback": mm components which don't have transparent hugepage
14 if necessary, split a transparent hugepage. Therefore these components
17 - if a hugepage allocation fails because of memory fragmentation,
30 is not specific to transparent hugepage support and it's a generic
37 get_user_pages and pin_user_pages if run on a hugepage, will return the
52 hugepage backed mappings.
59 pmd_offset. It's trivial to make the code transparent hugepage aware
64 hugepage aware.
66 If you're not walking pagetables but you run into a physical hugepage
69 it tries to swapout the hugepage for example. split_huge_page() can fail
[all …]
|
| /linux-6.12.1/Documentation/arch/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.12.1/mm/ |
| D | hugetlb_cgroup.c | 48 return &h_cg->hugepage[idx]; in __hugetlb_cgroup_counter_from_cgroup()
219 page_counter_charge(&parent->hugepage[idx], nr_pages); in hugetlb_cgroup_move_parent()
221 counter = &h_cg->hugepage[idx]; in hugetlb_cgroup_move_parent()
498 page_counter_read(&h_cg->hugepage[idx]) * PAGE_SIZE); in hugetlb_cgroup_read_numa_stat()
528 counter = &h_cg->hugepage[MEMFILE_IDX(cft->private)]; in hugetlb_cgroup_read_u64()
563 counter = &h_cg->hugepage[idx]; in hugetlb_cgroup_read_u64_max()
652 counter = &h_cg->hugepage[MEMFILE_IDX(of_cft(of)->private)]; in hugetlb_cgroup_reset()
|
| D | mempolicy.c | 2304 unsigned long addr, bool hugepage) in vma_alloc_folio_noprof() argument
|
| /linux-6.12.1/Documentation/admin-guide/mm/ |
| D | transhuge.rst | 74 entities). It doesn't require reservation to prevent hugepage
84 lived page allocations even for hugepage unaware applications that
119 where <size> is the hugepage size being addressed, the available sizes
126 Alternatively it is possible to specify that a given hugepage size
143 hugepage sizes have enabled="never". If enabling multiple hugepage
201 PMD-mappable transparent hugepage::
248 and how many milliseconds to wait in khugepaged if there's an hugepage
257 one 2M hugepage. Each may happen independently, or together, depending on
332 You can control hugepage allocation policy in tmpfs with mount option
354 There's also sysfs knob to control hugepage allocation policy for internal
[all …]
|
| D | hugetlbpage.rst | 66 is the default hugepage size (in kB).
146 It will allocate 1 2M hugepage on node0 and 2 2M hugepages on node1.
309 When adjusting the persistent hugepage count via ``nr_hugepages_mempolicy``, any
459 not hugepage aligned. For example, munmap(2) will fail if memory is backed by
460 a hugetlb page and the length is smaller than the hugepage size.
471 ``hugepage-shm``
472 see tools/testing/selftests/mm/hugepage-shm.c
474 ``hugepage-mmap``
475 see tools/testing/selftests/mm/hugepage-mmap.c
|
| D | userfaultfd.rst | 38 Vmas are not suitable for page- (or hugepage) granular fault tracking
|
| /linux-6.12.1/Documentation/ |
| D | dontdiff | 140 hugepage-mmap
141 hugepage-shm
|
| /linux-6.12.1/include/linux/ |
| D | gfp.h | 309 unsigned long addr, bool hugepage);
329 #define vma_alloc_folio_noprof(gfp, order, vma, addr, hugepage) \ argument
|
| D | hugetlb_cgroup.h | 41 struct page_counter hugepage[HUGE_MAX_HSTATE]; member
|
| /linux-6.12.1/Documentation/admin-guide/sysctl/ |
| D | vm.rst | 281 - For a page that is part of a transparent hugepage, soft-offline splits the
282 transparent hugepage into raw pages, then migrates only the raw error page.
283 As a result, user is transparently backed by 1 less hugepage, impacting
286 - For a page that is part of a HugeTLB hugepage, soft-offline first migrates
287 the entire HugeTLB hugepage, during which a free hugepage will be consumed
288 as migration target. Then the original hugepage is dissolved into raw
614 Change the minimum size of the hugepage pool.
659 Change the size of the hugepage pool at run-time on a specific
668 Change the maximum size of the hugepage pool. The maximum is
|
| /linux-6.12.1/Documentation/admin-guide/cgroup-v1/ |
| D | hugetlb.rst | 34 For a system supporting three hugepage sizes (64k, 32M and 1G), the control
|
| /linux-6.12.1/Documentation/trace/ |
| D | events-kmem.rst | 119 pageblock_size is usually the size of the default hugepage size.
|
| /linux-6.12.1/Documentation/translations/zh_CN/admin-guide/mm/damon/ |
| D | usage.rst | 220 - ``hugepage``: 为带有 ``MADV_HUGEPAGE`` 的区域调用 ``madvise()`` 。
|
| /linux-6.12.1/Documentation/translations/zh_TW/admin-guide/mm/damon/ |
| D | usage.rst | 220 - ``hugepage``: 爲帶有 ``MADV_HUGEPAGE`` 的區域調用 ``madvise()`` 。
|
| /linux-6.12.1/Documentation/mm/damon/ |
| D | design.rst | 339 - ``hugepage``: Call ``madvise()`` for the region with ``MADV_HUGEPAGE``.
|
| /linux-6.12.1/Documentation/ABI/stable/ |
| D | sysfs-block | 598 since its granularity is based on the hugepage size.
|
| /linux-6.12.1/Documentation/admin-guide/mm/damon/ |
| D | usage.rst | 762 - 3: ``hugepage``
|
| /linux-6.12.1/Documentation/filesystems/ |
| D | proc.rst | 523 "AnonHugePages" shows the amount of memory backed by transparent hugepage.
949 A page block is typically the size of the default hugepage size, e.g. 2MB on
|