Home
last modified time | relevance | path

Searched refs:HugeTLB (Results 1 – 15 of 15) sorted by relevance

/linux-6.6.21/Documentation/mm/
Dvmemmap_dedup.rst5 A vmemmap diet for HugeTLB and Device DAX
8 HugeTLB chapter
11 This section is to explain how HugeTLB Vmemmap Optimization (HVO) works.
17 HugeTLB pages consist of multiple base page size pages and is supported by many
19 details. On the x86-64 architecture, HugeTLB pages of size 2MB and 1GB are
20 currently supported. Since the base page size on x86 is 4KB, a 2MB HugeTLB page
21 consists of 512 base pages and a 1GB HugeTLB page consists of 262144 base pages.
24 Within the HugeTLB subsystem, only the first 4 ``struct page`` are used to
25 contain unique information about a HugeTLB page. ``__NR_USED_SUBPAGE`` provides
29 By removing redundant ``struct page`` for HugeTLB pages, memory can be returned
[all …]
Darch_pgtable_helpers.rst95 | pmd_huge | Tests a HugeTLB mapped PMD |
173 | pud_huge | Tests a HugeTLB mapped PUD |
219 HugeTLB Page Table Helpers
223 | pte_huge | Tests a HugeTLB |
225 | arch_make_huge_pte | Creates a HugeTLB |
227 | huge_pte_dirty | Tests a dirty HugeTLB |
229 | huge_pte_write | Tests a writable HugeTLB |
231 | huge_pte_mkdirty | Creates a dirty HugeTLB |
233 | huge_pte_mkwrite | Creates a writable HugeTLB |
235 | huge_pte_wrprotect | Creates a write protected HugeTLB |
[all …]
/linux-6.6.21/Documentation/admin-guide/cgroup-v1/
Dhugetlb.rst2 HugeTLB Controller
5 HugeTLB controller can be created by first mounting the cgroup filesystem.
9 With the above step, the initial or the parent HugeTLB group becomes
27 ….failcnt # show the number of allocation failure due to HugeTLB reservation limit
31 …>.failcnt # show the number of allocation failure due to HugeTLB usage limit
73 The HugeTLB controller allows users to limit the HugeTLB usage (page fault) per
74 control group and enforces the limit during page fault. Since HugeTLB
76 that, the application will get SIGBUS signal if it tries to fault in HugeTLB
78 HugeTLB pages it uses before hand, and the sysadmin needs to make sure that
90 The HugeTLB controller allows to limit the HugeTLB reservations per control
[all …]
/linux-6.6.21/Documentation/admin-guide/sysctl/
Dvm.rst572 Enable (set to 1) or disable (set to 0) HugeTLB Vmemmap Optimization (HVO).
574 Once enabled, the vmemmap pages of subsequent allocation of HugeTLB pages from
575 buddy allocator will be optimized (7 pages per 2MB HugeTLB page and 4095 pages
576 per 1GB HugeTLB page), whereas already allocated HugeTLB pages will not be
577 optimized. When those optimized HugeTLB pages are freed from the HugeTLB pool
580 again. If your use case is that HugeTLB pages are allocated 'on the fly' (e.g.
581 never explicitly allocating HugeTLB pages with 'nr_hugepages' but only set
582 'nr_overcommit_hugepages', those overcommitted HugeTLB pages are allocated 'on
583 the fly') instead of being pulled from the HugeTLB pool, you should weigh the
585 of allocation or freeing HugeTLB pages between the HugeTLB pool and the buddy
[all …]
/linux-6.6.21/fs/
DKconfig257 bool "HugeTLB file system support"
262 hugetlbfs is a filesystem backing for HugeTLB pages, based on
277 bool "HugeTLB Vmemmap Optimization (HVO) defaults to on"
281 The HugeTLB VmemmapvOptimization (HVO) defaults to off. Say Y here to
/linux-6.6.21/include/linux/
Dpage-flags.h820 SETPAGEFLAG(HugeTLB, hugetlb, PF_SECOND) in SETPAGEFLAG() argument
821 CLEARPAGEFLAG(HugeTLB, hugetlb, PF_SECOND) in SETPAGEFLAG()
/linux-6.6.21/arch/sh/mm/
DKconfig181 prompt "HugeTLB page size"
/linux-6.6.21/Documentation/admin-guide/mm/
Dpagemap.rst113 This is an integral part of a HugeTLB page.
Dhugetlbpage.rst2 HugeTLB Pages
165 When CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP is set, this enables HugeTLB
Dconcepts.rst83 memory with the huge pages. The first one is `HugeTLB filesystem`, or
Dmemory-hotplug.rst674 - Out of memory when dissolving huge pages, especially when HugeTLB Vmemmap
/linux-6.6.21/init/
DKconfig1090 bool "HugeTLB controller"
1095 Provides a cgroup controller for HugeTLB pages.
1096 When you enable this, you can put a per cgroup limit on HugeTLB usage.
1097 The limit is enforced during page fault. Since HugeTLB doesn't
1100 HugeTLB pages beyond its limit. This requires the application to know
1101 beforehand how much HugeTLB pages it would require for its use. The
/linux-6.6.21/Documentation/admin-guide/
Dcgroup-v2.rst67 5-8. HugeTLB
68 5.8-1. HugeTLB Interface Files
2388 HugeTLB section in Controllers
2391 The HugeTLB controller allows to limit the HugeTLB usage per control group and
2394 HugeTLB Interface Files argument
2409 The number of allocation failure due to HugeTLB limit
Dkernel-parameters.txt1008 [HW] The size of the default HugeTLB page. This is
1772 hugepages= [HW] Number of HugeTLB pages to allocate at boot.
1775 If this is the first HugeTLB parameter on the command
1784 [HW] The size of the HugeTLB pages. This is used in
1806 Control if HugeTLB Vmemmap Optimization (HVO) is enabled.
/linux-6.6.21/mm/
DKconfig504 # to enable the feature of HugeTLB/dev_dax vmemmap optimization.
698 HUGETLB_PAGE_ORDER when there are multiple HugeTLB page sizes available