| /dpdk/doc/guides/linux_gsg/ |
| H A D | sys_reqs.rst | 152 This is done by echoing the number of hugepages required
158 echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
165 echo 1024 > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages
166 echo 1024 > /sys/devices/system/node/node1/hugepages/hugepages-2048kB/nr_hugepages
168 The tool ``dpdk-hugepages.py`` can be used to manage hugepages.
180 it is preferable to reserve hugepages at boot time,
187 hugepages=1024
193 default_hugepagesz=1G hugepagesz=1G hugepages=4
198 If pse exists, 2M hugepages are supported; if pdpe1gb exists, 1G hugepages are supported.
219 mount points for hugepages need to be created.
[all …]
|
| H A D | linux_eal_parameters.rst | 102 Reused hugepages can contain data from previous processes that used them,
105 when all the hugepages mapped from them are freed,
110 Free hugepages back to system exactly as they were originally allocated.
|
| 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
159 …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.
|
| /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]
65 While any user can run the ``dpdk-hugepages.py`` script to view the
74 dpdk-hugepages.py -s
78 dpdk-hugepages.py -p 1G --setup 2G
|
| H A D | index.rst | 11 hugepages
|
| /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 no…
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 nohz_full=1,2
|
| H A D | lm_virtio_vhost_user.rst | 414 /root/dpdk/usertools/dpdk-hugepages.py --show
415 /root/dpdk/usertools/dpdk-hugepages.py --setup 2G
416 /root/dpdk/usertools/dpdk-hugepages.py --show
|
| H A D | lm_bond_virtio_sriov.rst | 584 /root/dpdk/usertools/dpdk-hugepages.py --show
585 /root/dpdk/usertools/dpdk-hugepages.py --setup 2G
586 /root/dpdk/usertools/dpdk-hugepages.py --show
|
| /dpdk/lib/eal/linux/ |
| H A D | eal_memory.c | 671 page_sz = hugepages[seg_start].size;
672 socket_id = hugepages[seg_start].socket_id;
719 struct hugepage_file *hfile = &hugepages[cur_page];
826 prealloc_segments(struct hugepage_file *hugepages, int n_pages) argument
841 struct hugepage_file *hpi = &hugepages[cur_page];
866 cur = &hugepages[cur_page];
868 &hugepages[cur_page - 1];
993 cur = &hugepages[cur_page];
994 prev = cur_page == 0 ? NULL : &hugepages[cur_page - 1];
1021 ret = remap_segment(hugepages, seg_start_page,
[all …]
|
| /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
|
| /dpdk/doc/guides/nics/ |
| H A D | build_and_test.rst | 67 echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
87 dpdk-hugepages.py --setup 2G
|
| H A D | cnxk.rst | 68 EAL: No available hugepages reported in hugepages-16777216kB
69 EAL: No available hugepages reported in hugepages-2048kB
|
| H A D | hns3.rst | 276 For 4K systems, 1 GB hugepages are recommended. For 64 KB systems, 512 MB
277 hugepages are recommended.
|
| /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 dpdk-hugepages.py --show
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 \
|
| /dpdk/usertools/ |
| H A D | meson.build | 8 'dpdk-hugepages.py',
|
| /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.
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | env_abstraction_layer.rst | 89 The allocation of large contiguous physical memory is done using hugepages.
99 are also backed by hugepages unless ``--no-huge`` option is given.
110 potentially result in hugepages being released back to the system.
169 not allow acquiring or releasing hugepages from the system at runtime.
234 Below is an overview of methods used for each OS to obtain hugepages,
239 to reserve a fixed number of hugepages at system start,
242 Windows EAL allocates hugepages from the OS as needed using Win32 API,
255 because secondary processes need to map the same hugepages.
272 This reduces the number of hugepages available to other processes
273 as reported by ``/sys/kernel/mm/hugepages/hugepages-*/free_hugepages``.
[all …]
|
| /dpdk/doc/guides/windows_gsg/ |
| H A D | run_apps.rst | 10 Use of hugepages ("large pages" in Windows terminology) requires
|
| /dpdk/doc/guides/cryptodevs/ |
| H A D | octeontx.rst | 110 dpdk-hugepages.py --setup 4G --pagesize 512M
|
| /dpdk/doc/guides/bbdevs/ |
| H A D | acc100.rst | 71 DPDK requires hugepages to be configured as detailed in section 2 of the DPDK manual.
72 The bbdev test application has been tested with a configuration 40 x 1GB hugepages. The
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_19_02.rst | 10 * **Added support for freeing hugepages exactly as originally allocated.**
25 * **Added support for using virtio-user without hugepages.**
29 hugepages.
|