Home
last modified time | relevance | path

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

123

/openbmc/linux/tools/testing/selftests/kvm/x86_64/
H A 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
H A 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()
/openbmc/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.
/openbmc/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
/openbmc/qemu/docs/
H A Dmemory-hotplug.txt54 For example, assuming that the host has 1GB hugepages available in
55 the /mnt/hugepages-1GB directory, a 1GB hugepage could be hotplugged
58 (qemu) object_add memory-backend-file,id=mem1,size=1G,mem-path=/mnt/hugepages-1GB
71 -object memory-backend-file,id=mem1,size=1G,mem-path=/mnt/hugepages-1G \
73 -object memory-backend-file,id=mem2,size=256M,mem-path=/mnt/hugepages-2MB \
/openbmc/linux/Documentation/admin-guide/mm/
H A 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 …]
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
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 …]
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-benchmark/libhugetlbfs/files/
H A D0007-Mark-glibc-specific-code-so.patch28 /* Set some allocator options more appropriate for hugepages */
35 * to mmap() if we run out of hugepages. */
/openbmc/qemu/docs/system/devices/
H A Divshmem.rst50 ivshmem and hugepages
58 …|qemu_system_x86| -object memory-backend-file,size=1G,mem-path=/dev/hugepages/my-shmem-file,share,…
61 ivshmem-server also supports hugepages mount points with the ``-m``
/openbmc/linux/tools/testing/selftests/kvm/
H A 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()
/openbmc/qemu/docs/devel/migration/
H A Dpostcopy.rst77 the first Discard being performed, hugepages are switched off
249 Postcopy with hugepages
254 a) The linux kernel on the destination must support userfault on hugepages.
257 c) Note that ``-mem-path /dev/hugepages`` will fall back to allocating normal
258 RAM if it doesn't have enough hugepages, triggering (b) to fail.
259 Using ``-mem-prealloc`` enforces the allocation using hugepages.
261 hugepages works well, however 1GB hugepages are likely to be problematic
/openbmc/linux/Documentation/features/vm/THP/
H A Darch-support.txt4 # description: arch supports transparent hugepages
/openbmc/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)
/openbmc/u-boot/board/freescale/ls2080a/
H A DREADME26 hugepages=16 mem=2048M'
/openbmc/u-boot/configs/
H A Dls2080a_emu_defconfig13 …n=uart8250,mmio,0x21c0500 ramdisk_size=0x2000000 default_hugepagesz=2m hugepagesz=2m hugepages=256"
H A Dlx2160aqds_tfa_defconfig15 …1c0000 ramdisk_size=0x2000000 default_hugepagesz=1024m hugepagesz=1024m hugepages=2 pci=pcie_bus_p…
H A Dls2080a_simu_defconfig13 …n=uart8250,mmio,0x21c0500 ramdisk_size=0x2000000 default_hugepagesz=2m hugepagesz=2m hugepages=256"
H A Dlx2160ardb_tfa_defconfig16 …1c0000 ramdisk_size=0x2000000 default_hugepagesz=1024m hugepagesz=1024m hugepages=2 pci=pcie_bus_p…
H A Dls1088aqds_defconfig13 …n=uart8250,mmio,0x21c0500 ramdisk_size=0x3000000 default_hugepagesz=2m hugepagesz=2m hugepages=256"
H A Dlx2160ardb_tfa_SECURE_BOOT_defconfig16 …1c0000 ramdisk_size=0x2000000 default_hugepagesz=1024m hugepagesz=1024m hugepages=2 pci=pcie_bus_p…
H A Dls1088aqds_qspi_defconfig15 …n=uart8250,mmio,0x21c0500 ramdisk_size=0x3000000 default_hugepagesz=2m hugepagesz=2m hugepages=256"
H A Dls2081ardb_defconfig15 …n=uart8250,mmio,0x21c0600 ramdisk_size=0x2000000 default_hugepagesz=2m hugepagesz=2m hugepages=256"
H A Dlx2160aqds_tfa_SECURE_BOOT_defconfig15 …1c0000 ramdisk_size=0x2000000 default_hugepagesz=1024m hugepagesz=1024m hugepages=2 pci=pcie_bus_p…
/openbmc/linux/tools/testing/selftests/iommu/
H A 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()

123