Home
last modified time | relevance | path

Searched refs:hugepages (Results 1 – 25 of 28) sorted by relevance

12

/linux/tools/testing/selftests/kvm/x86/
H A Ddirty_log_page_splitting_test.c39 u64 hugepages; member
47 stats->hugepages = stats->pages_2m + stats->pages_1g; in get_page_stats()
51 stats->hugepages); in get_page_stats()
183 TEST_ASSERT_EQ(stats_clear_pass[0].hugepages, 0); in run_test()
187 TEST_ASSERT_EQ(stats_dirty_logging_enabled.hugepages, stats_populated.hugepages); in run_test()
189 TEST_ASSERT_EQ(stats_dirty_logging_enabled.hugepages, 0); in run_test()
/linux/Documentation/ABI/testing/
H A Dsysfs-kernel-mm-hugepages1 What: /sys/kernel/mm/hugepages/
5 /sys/kernel/mm/hugepages/ contains a number of subdirectories
6 of the form hugepages-<size>kB, where <size> is the page size
7 of the hugepages supported by the kernel/CPU combination.
/linux/Documentation/arch/arm64/
H A Dhugetlbpage.rst10 - the size of hugepages
13 The ARM64 port supports two flavours of hugepages.
18 These are regular hugepages where a pmd or a pud page table entry points to a
/linux/Documentation/admin-guide/mm/
H A Dtranshuge.rst44 hugepages but a significant speedup already happens if only one of
45 the two is using hugepages just because of the fact the TLB miss is
78 hugepages. It requires no modifications for applications to take
88 In certain cases when hugepages are enabled system wide, application
92 possible to disable hugepages system-wide and to only have them inside
95 Embedded systems should enable hugepages only inside madvise regions
99 Applications that gets a lot of benefit from hugepages and that don't
100 risk to lose memory by using hugepages, should use
116 echo always >/sys/kernel/mm/transparent_hugepage/hugepages-<size>kB/enabled
117 echo madvise >/sys/kernel/mm/transparent_hugepage/hugepages
[all...]
/linux/tools/testing/selftests/mm/
H A Dthp_settings.c
H A Dprctl_thp_disable.c146 self->settings.hugepages[sz2ord(self->pmdsize, getpagesize())].enabled = THP_INHERIT; in FIXTURE_SETUP()
254 self->settings.hugepages[sz2ord(self->pmdsize, getpagesize())].enabled = THP_INHERIT; in FIXTURE_SETUP()
H A Dthp_settings.h
H A Duffd-wp-mremap.c96 settings.hugepages[sz2ord(size, pagesize)].enabled = THP_ALWAYS; in alloc_one_folio()
362 settings.hugepages[i].enabled = THP_NEVER; in main()
H A Dcharge_reserved_hugetlb.sh98 # For 1GB hugepages
102 # For 2MB hugepages
311 echo nr hugepages = "$nr_hugepages"
366 echo nr hugepages = "$nr_hugepages"
H A Dcow.c1226 settings.hugepages[sz2ord(pmdsize, pagesize)].enabled = THP_NEVER; in run_anon_test_case()
1227 settings.hugepages[sz2ord(size, pagesize)].enabled = THP_ALWAYS; in run_anon_test_case()
1891 default_settings.hugepages[sz2ord(pmdsize, pagesize)].enabled = THP_INHERIT; in main()
H A Dkhugepaged.c1251 default_settings.hugepages[hpage_pmd_order].enabled = THP_INHERIT; in main()
1252 default_settings.hugepages[anon_order].enabled = THP_ALWAYS; in main()
H A Drun_vmtests.sh186 # On memory constrainted systems some tests can fail to allocate hugepages.
/linux/tools/testing/selftests/kvm/
H A Dmmu_stress_test.c287 bool hugepages = false; in main() local
320 hugepages = true; in main()
343 fd = kvm_memfd_alloc(slot_size, hugepages); in main()
/linux/tools/testing/selftests/iommu/
H A Diommufd.c1645 bool hugepages; in FIXTURE_SETUP()
1669 if (variant->hugepages) { in FIXTURE_VARIANT_ADD()
1687 .hugepages = false, in FIXTURE_VARIANT_ADD()
1694 .hugepages = false, in FIXTURE_VARIANT_ADD()
1701 .hugepages = true, in FIXTURE_VARIANT_ADD()
1708 .hugepages = true, in FIXTURE_VARIANT_ADD()
1715 .hugepages = false,
1722 .hugepages = true,
1841 size_t test_step = variant->hugepages ? (self->mmap_buf_size / 16) : in TEST_F()
1864 if (variant->hugepages) in TEST_F()
1630 bool hugepages; FIXTURE_VARIANT() local
2094 bool hugepages; FIXTURE_VARIANT() local
[all...]
/linux/Documentation/features/vm/THP/
H A Darch-support.txt4 # description: arch supports transparent hugepages
/linux/drivers/gpu/drm/i915/selftests/
H A Di915_mock_selftests.h34 selftest(hugepages, i915_gem_huge_page_mock_selftests)
H A Di915_live_selftests.h40 selftest(hugepages, i915_gem_huge_page_live_selftests)
/linux/arch/loongarch/kvm/
H A Dmmu.c94 kvm->stat.hugepages--; in kvm_flush_pte()
747 kvm->stat.hugepages--; in kvm_split_huge()
897 ++kvm->stat.hugepages; in kvm_map_page()
H A Dvm.c16 STATS_DESC_ICOUNTER(VM, hugepages),
/linux/arch/loongarch/include/asm/
H A Dkvm_host.h55 u64 hugepages;
54 u64 hugepages; global() member
/linux/tools/testing/selftests/kvm/lib/
H A Dkvm_util.c851 int kvm_memfd_alloc(size_t size, bool hugepages)
856 if (hugepages) in kvm_memfd_alloc()
852 kvm_memfd_alloc(size_t size,bool hugepages) kvm_memfd_alloc() argument
/linux/tools/testing/selftests/kvm/include/
H A Dkvm_util.h476 int kvm_memfd_alloc(size_t size, bool hugepages);
/linux/Documentation/admin-guide/
H A Dcgroup-v2.rst1606 transparent hugepages
1610 hugepages
1614 transparent hugepages
1743 Number of transparent hugepages which were allocated to satisfy
1748 Number of transparent hugepages which were allocated to allow
1753 Number of transparent hugepages which are swapout in one piece
1757 Number of transparent hugepages which were split before swapout.
H A Dkernel-parameters.txt1205 the size represented by the legacy /proc/ hugepages
2034 hugepages= [HW,EARLY] Number of HugeTLB pages to allocate at boot.
2047 used in conjunction with hugepages (above) to
2049 pair hugepagesz=X hugepages=Y can be specified once
2057 allocate hugepages during boot. This option can be
2065 of gigantic hugepages. Or using node format, the size
2075 hugepages using the CMA allocator. If enabled, the
2076 boot-time allocation of gigantic hugepages is skipped.
7552 to anonymous transparent hugepages.
7835 with respect to transparent hugepages
[all...]
/linux/Documentation/virt/kvm/x86/
H A Dmmu.rst30 hugepages, and similar features work without change

12