Home
last modified time | relevance | path

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

/linux-6.6.21/tools/testing/selftests/kvm/x86_64/
Dnx_huge_pages_test.sh14 HUGE_PAGES=$(cat /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages)
32 sudo_echo "$(( $HUGE_PAGES + 3 ))" /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
56 sudo_echo "$HUGE_PAGES" /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
Ddirty_log_page_splitting_test.c38 uint64_t hugepages; member
46 stats->hugepages = stats->pages_2m + stats->pages_1g; in get_page_stats()
50 stats->hugepages); in get_page_stats()
182 TEST_ASSERT_EQ(stats_clear_pass[0].hugepages, 0); in run_test()
184 TEST_ASSERT_EQ(stats_dirty_logging_enabled.hugepages, stats_populated.hugepages); in run_test()
186 TEST_ASSERT_EQ(stats_dirty_logging_enabled.hugepages, 0); in run_test()
/linux-6.6.21/Documentation/ABI/testing/
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-6.6.21/Documentation/arch/arm64/
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-6.6.21/Documentation/admin-guide/mm/
Dhugetlbpage.rst73 ``/sys/kernel/mm/hugepages`` (described below).
99 command line by specifying the "hugepages=N" parameter, where 'N' = the
112 Specify a huge page size. Used in conjunction with hugepages
114 size. Hence, hugepagesz and hugepages are typically specified in
117 hugepagesz=2M hugepages=512
122 hugepages
125 if hugepages is the first or only hugetlb command line parameter it
128 specified, it can not be overwritten by a hugepagesz,hugepages
135 hugepages=256 hugepagesz=2M hugepages=512
138 indicating that the hugepages=512 parameter is ignored. If a hugepages
[all …]
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
62 hugepages. It requires no modifications for applications to take
72 In certain cases when hugepages are enabled system wide, application
76 possible to disable hugepages system-wide and to only have them inside
79 Embedded systems should enable hugepages only inside madvise regions
83 Applications that gets a lot of benefit from hugepages and that don't
84 risk to lose memory by using hugepages, should use
105 anonymous hugepages in case they're not immediately free to madvise
107 pages unless hugepages are immediately available. Clearly if we spend CPU
[all …]
Dpagemap.rst121 Contiguous pages which construct transparent hugepages.
/linux-6.6.21/tools/testing/selftests/kvm/
Dmax_guest_memory_test.c172 bool hugepages = false; in main() local
205 hugepages = true; in main()
222 fd = kvm_memfd_alloc(slot_size, hugepages); in main()
/linux-6.6.21/Documentation/features/vm/THP/
Darch-support.txt4 # description: arch supports transparent hugepages
/linux-6.6.21/drivers/gpu/drm/i915/selftests/
Di915_mock_selftests.h34 selftest(hugepages, i915_gem_huge_page_mock_selftests)
Di915_live_selftests.h40 selftest(hugepages, i915_gem_huge_page_live_selftests)
/linux-6.6.21/tools/testing/selftests/iommu/
Diommufd.c1080 bool hugepages; in FIXTURE_VARIANT() local
1100 if (variant->hugepages) { in FIXTURE_SETUP()
1118 .hugepages = false, in FIXTURE_VARIANT_ADD()
1124 .hugepages = false, in FIXTURE_VARIANT_ADD()
1130 .hugepages = true, in FIXTURE_VARIANT_ADD()
1136 .hugepages = true, in FIXTURE_VARIANT_ADD()
1216 size_t test_step = variant->hugepages ? (self->mmap_buf_size / 16) : in TEST_F()
1233 if (variant->hugepages) in TEST_F()
1257 size_t test_step = variant->hugepages ? self->mmap_buf_size / 16 : in TEST_F()
1274 if (variant->hugepages) in TEST_F()
/linux-6.6.21/Documentation/mm/
Dtranshuge.rst22 - if some task quits and more hugepages become available (either
24 backed by regular pages should be relocated on hugepages
27 - it doesn't require memory reservation and in turn it uses hugepages
/linux-6.6.21/tools/testing/selftests/mm/
Dcharge_reserved_hugetlb.sh285 echo nr hugepages = "$nr_hugepages"
338 echo nr hugepages = "$nr_hugepages"
/linux-6.6.21/Documentation/ABI/stable/
Dsysfs-devices-node88 What: /sys/devices/system/node/nodeX/hugepages/hugepages-<size>/
/linux-6.6.21/tools/testing/selftests/kvm/lib/
Dkvm_util.c736 int kvm_memfd_alloc(size_t size, bool hugepages) in kvm_memfd_alloc() argument
741 if (hugepages) in kvm_memfd_alloc()
/linux-6.6.21/tools/testing/selftests/kvm/include/
Dkvm_util_base.h345 int kvm_memfd_alloc(size_t size, bool hugepages);
/linux-6.6.21/Documentation/admin-guide/cgroup-v1/
Dmemory.rst544 transparent hugepages).
545 rss_huge # of bytes of anonymous transparent hugepages.
/linux-6.6.21/Documentation/virt/kvm/x86/
Dmmu.rst30 hugepages, and similar features work without change
/linux-6.6.21/Documentation/admin-guide/
Dcgroup-v2.rst1424 transparent hugepages
1428 hugepages
1432 transparent hugepages
1526 Number of transparent hugepages which were allocated to satisfy
1531 Number of transparent hugepages which were allocated to allow
Dkernel-parameters.txt1009 the size represented by the legacy /proc/ hugepages
1772 hugepages= [HW] Number of HugeTLB pages to allocate at boot.
1785 conjunction with hugepages (above) to allocate huge
1787 hugepagesz=X hugepages=Y can be specified once for
1794 of gigantic hugepages. Or using node format, the size
1800 hugepages using the CMA allocator. If enabled, the
1801 boot-time allocation of gigantic hugepages is skipped.
6564 with respect to transparent hugepages.
/linux-6.6.21/arch/
DKconfig926 # must be used to enable allocations to use hugepages.
/linux-6.6.21/Documentation/virt/kvm/
Dapi.rst4493 present for the addresses (e.g. when using hugepages).
4622 hugepages).
/linux-6.6.21/
DMAINTAINERS9662 F: Documentation/ABI/testing/sysfs-kernel-mm-hugepages