Searched refs:GB (Results 1 – 18 of 18) sorted by relevance
| /dpdk/app/test/ |
| H A D | test_malloc_perf.c | 21 static const uint64_t GB = 1 << 30; variable 40 ptr = rte_malloc(NULL, GB, 0); in test_memset_perf() 42 TEST_LOG(ERR, "rte_malloc(size=%"PRIx64") failed\n", GB); in test_memset_perf() 48 memset(ptr, 0, GB); in test_memset_perf() 119 memset_gb_us * size / GB; in test_alloc_perf()
|
| /dpdk/doc/guides/gpus/ |
| H A D | cuda.rst | 179 - NVIDIA A100 80GB PCIe 180 - NVIDIA A100 40GB PCIe 181 - NVIDIA A30 24GB 182 - NVIDIA A10 24GB 183 - NVIDIA V100 32GB PCIe 184 - NVIDIA V100 16GB PCIe
|
| /dpdk/doc/guides/linux_gsg/ |
| H A D | sys_reqs.rst | 172 Some kernel versions may not allow reserving 1 GB hugepages at run time, 199 On IBM Power architecture, the supported hugepage sizes are 16MB and 16GB. 203 For 64-bit applications, it is recommended to use 1 GB hugepages if the platform supports them. 226 to manually create mount points for those hugepage sizes (e.g. 1GB pages). 228 To make the hugepages of size 1GB available for DPDK use, 232 mount -t hugetlbfs pagesize=1GB /mnt/huge 236 nodev /mnt/huge hugetlbfs pagesize=1GB 0 0
|
| H A D | nic_perf_intel_platform.rst | 15 …y channel has at least one memory DIMM inserted, and that the memory size for each is at least 4GB.
|
| H A D | build_sample_apps.rst | 179 Similarly, on a four socket system, to allocate 1 GB memory on each of sockets 0 and 2 only, the pa…
|
| /dpdk/license/ |
| H A D | exceptions.txt | 13 SPDX Identifier TB Approval Date GB Approval Date File name
|
| /dpdk/doc/guides/faq/ |
| H A D | faq.rst | 40 … is available, hence the number of hugepages they are able to allocate is also limited (1 GB size). 41 If your system has a lot (>1 GB size) of hugepage memory, not all of it will be allocated. 47 To avoid this scenario, either lower the amount of hugepage memory available to 1 GB size (or less)…
|
| /dpdk/doc/guides/nics/ |
| H A D | enetfec.rst | 35 It has only 1 GB Ethernet interface with RJ45 connector.
|
| H A D | hns3.rst | 256 32 GB DIMMs is used to ensure that each channel is fully configured. 276 For 4K systems, 1 GB hugepages are recommended. For 64 KB systems, 512 MB
|
| H A D | enic.rst | 599 PMD. Typically, the limit has to be raised to higher than 2GB.
|
| /dpdk/doc/guides/freebsd_gsg/ |
| H A D | install_from_ports.rst | 96 EAL: Contigmem driver has 2 buffers, each of size 1GB
|
| /dpdk/doc/guides/bbdevs/ |
| H A D | acc100.rst | 72 The bbdev test application has been tested with a configuration 40 x 1GB hugepages. The
|
| H A D | fpga_5gnr_fec.rst | 57 The bbdev test application has been tested with a configuration 40 x 1GB hugepages. The
|
| H A D | fpga_lte_fec.rst | 56 The bbdev test application has been tested with a configuration 40 x 1GB hugepages. The
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_2_2.rst | 437 calculated limiting the size to 4GB.
|
| H A D | known_issues.rst | 366 If using 2 MB hugepages, consider switching to a fewer number of 1 GB pages.
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | ipsec_secgw.rst | 275 * The ``--socket-mem`` to use 2GB on socket 1.
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | env_abstraction_layer.rst | 629 Memory zones can also be reserved from either 2 MB or 1 GB hugepages, provided that both are availa…
|