| /f-stack/dpdk/doc/guides/linux_gsg/ |
| H A D | sys_reqs.rst | 161 The reservation of hugepages can be performed at run time. 162 This is done by echoing the number of hugepages required 168 echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages 175 echo 1024 > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages 176 echo 1024 > /sys/devices/system/node/node1/hugepages/hugepages-2048kB/nr_hugepages 188 it is preferable to reserve hugepages at boot time, 195 hugepages=1024 201 default_hugepagesz=1G hugepagesz=1G hugepages=4 206 If pse exists, 2M hugepages are supported; if pdpe1gb exists, 1G hugepages are supported. 227 mount points for hugepages need to be created. [all …]
|
| H A D | build_sample_apps.rst | 59 Memory to allocate from hugepages on specific sockets. In dynamic memory mode, 73 Memory to allocate from hugepages, regardless of processor socket. It is 154 …an application, it is recommended to use the same amount of memory as that allocated for hugepages.
|
| H A D | nic_perf_intel_platform.rst | 116 default_hugepagesz=1G hugepagesz=1G hugepages=8 141 # Unmount the hugepages.
|
| H A D | linux_eal_parameters.rst | 93 Free hugepages back to system exactly as they were originally allocated.
|
| /f-stack/doc/ |
| H A D | F-Stack_Quick_Start_Guide.md | 28 echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages 32 echo 1024 > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages 33 echo 1024 > /sys/devices/system/node/node1/hugepages/hugepages-2048kB/nr_hugepages
|
| H A D | Launch_F-Stack_on_AWS_EC2_in_one_minute.md | 18 echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
|
| /f-stack/dpdk/doc/guides/tools/ |
| H A D | hugepages.rst | 4 dpdk-hugepages Application 7 The ``dpdk-hugepages`` tool is a Data Plane Development Kit (DPDK) utility 8 that helps in reserving hugepages. 19 dpdk-hugepages [options]
|
| H A D | index.rst | 14 hugepages
|
| /f-stack/dpdk/doc/guides/howto/ |
| H A D | virtio_user_for_container_networking.rst | 50 (aka, hugepages initialized in DPDK) are sent to backend. It restricts that only 89 -v /dev/hugepages:/dev/hugepages \ 105 * Cannot work when there are more than VHOST_MEMORY_MAX_NREGIONS(8) hugepages. 106 If you have more regions (especially when 2MB hugepages are used), the option, 110 * Root privilege is a must. DPDK resolves physical addresses of hugepages
|
| H A D | pvp_reference_benchmark.rst | 51 …intel_pstate=disable mce=ignore_ce default_hugepagesz=1G hugepagesz=1G hugepages=6 isolcpus=2-7 rc… 165 -object memory-backend-file,id=mem,size=3072M,mem-path=/dev/hugepages,share=on \ 218 important information (hugepages, vCPU pinning, Virtio PCI devices): 226 <hugepages> 228 </hugepages> 281 …default_hugepagesz=1G hugepagesz=1G hugepages=1 intel_iommu=on iommu=pt isolcpus=1,2 rcu_nocbs=1,2…
|
| H A D | lm_virtio_vhost_user.rst | 414 cat /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages 415 echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages 416 cat /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
|
| H A D | lm_bond_virtio_sriov.rst | 584 cat /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages 585 echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages 586 cat /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
|
| /f-stack/dpdk/lib/librte_eal/linux/ |
| H A D | eal_memory.c | 680 page_sz = hugepages[seg_start].size; 681 socket_id = hugepages[seg_start].socket_id; 728 struct hugepage_file *hfile = &hugepages[cur_page]; 835 prealloc_segments(struct hugepage_file *hugepages, int n_pages) argument 850 struct hugepage_file *hpi = &hugepages[cur_page]; 875 cur = &hugepages[cur_page]; 877 &hugepages[cur_page - 1]; 1002 cur = &hugepages[cur_page]; 1003 prev = cur_page == 0 ? NULL : &hugepages[cur_page - 1]; 1030 ret = remap_segment(hugepages, seg_start_page, [all …]
|
| /f-stack/dpdk/doc/guides/faq/ |
| H A D | faq.rst | 12 If I want to change the number of hugepages allocated, how do I remove the original pages allocated? 21 …t application, it looks to see if the pages are available in the ``/dev/hugepages`` directory and … 28 …p 3", I get the following output, indicating that there are no socket 0 hugepages to allocate the … 40 …s in terms of how much virtual memory is available, hence the number of hugepages they are able to… 42 Due to hugepages typically being allocated on a local NUMA node, the hugepages allocation the appli… 45 therefore all the hugepages are allocated on the wrong socket. 56 In this way, the hugepages have a greater chance of being allocated to the correct socket. 57 …e used to ensure the availability of memory for each socket, so that if hugepages were allocated on
|
| /f-stack/dpdk/doc/guides/sample_app_ug/ |
| H A D | vhost.rst | 56 -m $mem -object memory-backend-file,id=mem,size=$mem,mem-path=/dev/hugepages,share=on \ 186 insufficient hugepages being free to support the allocation request. The 187 number of free hugepages can be checked as follows: 191 cat /sys/kernel/mm/hugepages/hugepages-<pagesize>/nr_hugepages 193 The command above indicates how many hugepages are free to support QEMU's
|
| H A D | vhost_blk.rst | 50 mem-path=/dev/hugepages,share=on -numa node,memdev=mem \
|
| H A D | vhost_crypto.rst | 71 mem-path=/dev/hugepages,share=on -numa node,memdev=mem \
|
| /f-stack/dpdk/usertools/ |
| H A D | meson.build | 8 'dpdk-hugepages.py'
|
| /f-stack/ |
| H A D | README.md | 50 echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages 53 echo 1024 > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages 54 echo 1024 > /sys/devices/system/node/node1/hugepages/hugepages-2048kB/nr_hugepages
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | build_and_test.rst | 51 echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
|
| H A D | octeontx2.rst | 70 EAL: No available hugepages reported in hugepages-2048kB
|
| /f-stack/dpdk/doc/guides/cryptodevs/ |
| H A D | octeontx.rst | 110 echo 8 > /sys/kernel/mm/hugepages/hugepages-524288kB/nr_hugepages
|
| H A D | octeontx2.rst | 122 echo 8 > /sys/kernel/mm/hugepages/hugepages-524288kB/nr_hugepages
|
| /f-stack/dpdk/doc/guides/freebsd_gsg/ |
| H A D | build_sample_apps.rst | 81 Memory to allocate from hugepages, regardless of processor socket. 86 Memory to allocate from hugepages on specific sockets.
|
| /f-stack/dpdk/doc/guides/windows_gsg/ |
| H A D | run_apps.rst | 10 Use of hugepages ("large pages" in Windows terminology) requires
|