Home
last modified time | relevance | path

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

/Linux-v6.1/tools/testing/selftests/kvm/x86_64/
Dnx_huge_pages_test.sh15 HUGE_PAGES=$(cat /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages)
33 sudo_echo "$(( $HUGE_PAGES + 3 ))" /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
57 sudo_echo "$HUGE_PAGES" /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
/Linux-v6.1/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-v6.1/Documentation/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-v6.1/Documentation/admin-guide/mm/
Dhugetlbpage.rst75 ``/sys/kernel/mm/hugepages`` (described below).
101 command line by specifying the "hugepages=N" parameter, where 'N' = the
114 Specify a huge page size. Used in conjunction with hugepages
116 size. Hence, hugepagesz and hugepages are typically specified in
119 hugepagesz=2M hugepages=512
124 hugepages
127 if hugepages is the first or only hugetlb command line parameter it
130 specified, it can not be overwritten by a hugepagesz,hugepages
137 hugepages=256 hugepagesz=2M hugepages=512
140 indicating that the hugepages=512 parameter is ignored. If a hugepages
[all …]
Dtranshuge.rst46 hugepages but a significant speedup already happens if only one of
47 the two is using hugepages just because of the fact the TLB miss is
64 hugepages. It requires no modifications for applications to take
74 In certain cases when hugepages are enabled system wide, application
78 possible to disable hugepages system-wide and to only have them inside
81 Embedded systems should enable hugepages only inside madvise regions
85 Applications that gets a lot of benefit from hugepages and that don't
86 risk to lose memory by using hugepages, should use
107 anonymous hugepages in case they're not immediately free to madvise
109 pages unless hugepages are immediately available. Clearly if we spend CPU
[all …]
Dpagemap.rst124 Contiguous pages which construct transparent hugepages.
/Linux-v6.1/tools/testing/selftests/kvm/
Dmax_guest_memory_test.c172 bool hugepages = false; in main() local
208 hugepages = true; in main()
225 fd = kvm_memfd_alloc(slot_size, hugepages); in main()
/Linux-v6.1/Documentation/features/vm/THP/
Darch-support.txt4 # description: arch supports transparent hugepages
/Linux-v6.1/drivers/gpu/drm/i915/selftests/
Di915_mock_selftests.h34 selftest(hugepages, i915_gem_huge_page_mock_selftests)
Di915_live_selftests.h39 selftest(hugepages, i915_gem_huge_page_live_selftests)
/Linux-v6.1/tools/testing/selftests/vm/
Dcharge_reserved_hugetlb.sh285 echo nr hugepages = "$nr_hugepages"
338 echo nr hugepages = "$nr_hugepages"
/Linux-v6.1/Documentation/mm/
Dtranshuge.rst24 - if some task quits and more hugepages become available (either
26 backed by regular pages should be relocated on hugepages
29 - it doesn't require memory reservation and in turn it uses hugepages
/Linux-v6.1/Documentation/ABI/stable/
Dsysfs-devices-node88 What: /sys/devices/system/node/nodeX/hugepages/hugepages-<size>/
/Linux-v6.1/tools/testing/selftests/kvm/lib/
Dkvm_util.c625 int kvm_memfd_alloc(size_t size, bool hugepages) in kvm_memfd_alloc() argument
630 if (hugepages) in kvm_memfd_alloc()
/Linux-v6.1/tools/testing/selftests/kvm/include/
Dkvm_util_base.h286 int kvm_memfd_alloc(size_t size, bool hugepages);
/Linux-v6.1/Documentation/admin-guide/cgroup-v1/
Dmemory.rst530 transparent hugepages).
531 rss_huge # of bytes of anonymous transparent hugepages.
/Linux-v6.1/Documentation/virt/kvm/x86/
Dmmu.rst30 hugepages, and similar features work without change
/Linux-v6.1/Documentation/admin-guide/
Dcgroup-v2.rst1423 transparent hugepages
1427 hugepages
1431 transparent hugepages
1519 Number of transparent hugepages which were allocated to satisfy
1524 Number of transparent hugepages which were allocated to allow
Dkernel-parameters.txt973 the size represented by the legacy /proc/ hugepages
1710 hugepages= [HW] Number of HugeTLB pages to allocate at boot.
1723 conjunction with hugepages (above) to allocate huge
1725 hugepagesz=X hugepages=Y can be specified once for
1732 of gigantic hugepages. Or using node format, the size
1738 hugepages using the CMA allocator. If enabled, the
1739 boot-time allocation of gigantic hugepages is skipped.
6277 with respect to transparent hugepages.
/Linux-v6.1/arch/
DKconfig871 # must be used to enable allocations to use hugepages.
/Linux-v6.1/Documentation/virt/kvm/
Dapi.rst4570 present for the addresses (e.g. when using hugepages).
4618 hugepages).
/Linux-v6.1/
DMAINTAINERS9445 F: Documentation/ABI/testing/sysfs-kernel-mm-hugepages