Home
last modified time | relevance | path

Searched refs:hugepage (Results 1 – 25 of 32) sorted by relevance

12

/dpdk/doc/guides/linux_gsg/
H A Dsys_reqs.rst143 By using hugepage allocations, performance is increased since fewer pages are needed,
189 For other hugepage sizes, for example 1G pages, the size must be specified explicitly and
190 can also be optionally set as the default hugepage size for the system.
191 For example, to reserve 4G of hugepage memory in the form of four 1G pages, the following options s…
197 … The hugepage sizes that a CPU supports can be determined from the CPU flags on Intel architecture.
199 On IBM Power architecture, the supported hugepage sizes are 16MB and 16GB.
222 This mount point will use the default hugepage size
225 However, in order to use hugepage sizes other than the default, it is necessary
226 to manually create mount points for those hugepage sizes (e.g. 1GB pages).
H A Dlinux_eal_parameters.rst90 existing hugepage files are removed and re-created
94 hugepage files are also removed before mapping them,
98 When ``--huge-unlink=never`` is specified, existing hugepage files
99 are never removed, but are remapped instead, allowing hugepage reuse.
H A Dbuild_sample_apps.rst89 The prefix text used for hugepage filenames.
164 … also fail if the user requests less memory than the reserved amount of hugepage-memory, particula…
169 * The hugepage memory by be given to the application by the kernel in socket 1 only.
H A Dnic_perf_intel_platform.rst135 # Get the hugepage size.
144 # Create the hugepage mount folder.
H A Denable_func.rst20 * All directories which serve as hugepage mount points, for example, ``/dev/hugepages``
H A Dlinux_drivers.rst175 mapped in hugepage granularity or system page granularity. Number of DMA
177 for system/hugepage memory. Another per-container overall limit applicable both
/dpdk/lib/eal/linux/
H A Deal_memory.c1103 struct hugepage_file *hugepage = NULL, *tmp_hp = NULL; local
1374 hugepage = create_shared_memory(eal_hugepage_data_path(),
1377 if (hugepage == NULL) {
1381 memset(hugepage, 0, nr_hugefiles * sizeof(struct hugepage_file));
1398 if (copy_hugepages_to_shared_mem(hugepage, nr_hugefiles,
1407 prealloc_segments(hugepage, nr_hugefiles)) {
1416 if (remap_needed_hugepages(hugepage, nr_hugefiles)) {
1432 munmap(hugepage, nr_hugefiles * sizeof(struct hugepage_file));
1433 hugepage = NULL;
1471 if (hugepage != NULL)
[all …]
/dpdk/doc/guides/nics/
H A Dbuild_and_test.rst60 hugepage size configured in the system and calculate the number of pages
71 Check ``/proc/meminfo`` to find system hugepage size:
H A Dvhost.rst95 Other basic DPDK preparations like hugepage enabling here.
H A Dvmxnet3.rst123 hugepage enabling, UIO port binding are not listed here.
/dpdk/doc/guides/howto/
H A Dvirtio_user_for_container_networking.rst101 * Cannot work with --huge-unlink option. As we need to reopen the hugepage
109 will bring confusion when sharing hugepage files with backend by name.
/dpdk/doc/guides/prog_guide/
H A Dmulti_proc_support.rst16 each with different permissions on the hugepage memory used by the applications.
26 after a primary process has already configured the hugepage shared memory for them.
101 In this case, extensive use of rte_ring objects is made, which are located in shared hugepage memor…
114 By default, the EAL creates hugepage files on each hugetlbfs filesystem using the rtemap_X filename,
127 specify how much hugepage memory, in megabytes, each process can use (or passing
128 ``--socket-mem`` to specify how much hugepage memory on each socket each process
155 * The multi-process feature requires that the exact same hugepage memory mappings be present in a…
H A Denv_abstraction_layer.rst74 During the initialization of EAL resources such as hugepage backed memory can be
172 hugepage memory will be preallocated.
203 All possible virtual memory space that can ever be used for hugepage mapping in
251 * map each hugepage from its own file (the default)
258 (or in the mount point for a specific hugepage size).
262 Each backing file by default corresponds to one hugepage,
263 it is opened and locked for the entire time the hugepage is used.
268 In dynamic memory mode, EAL removes a backing hugepage file
282 to prevent data leaks from previous users of the same hugepage.
288 Clearing memory constitutes more than 95% of hugepage mapping time.
[all …]
/dpdk/doc/guides/tools/
H A Dhugepages.rst51 Select hugepage size to use.
/dpdk/doc/guides/faq/
H A Dfaq.rst41 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)…
186 How can hugepage-backed memory be shared among multiple processes?
/dpdk/doc/guides/sample_app_ug/
H A Dbbdev_app.rst108 * ``--file-prefix``: Prefix for hugepage filenames
H A Dmulti_process.rst48 meaning they have control over the hugepage shared memory regions.
194 once the hugepage shared memory and the network ports are initialized,
289 …t the server process stores its port configuration data in a memory zone in hugepage shared memory.
/dpdk/doc/guides/freebsd_gsg/
H A Dbuild_sample_apps.rst95 The prefix text used for hugepage filenames.
/dpdk/doc/guides/bbdevs/
H A Dacc100.rst73 hugepage configuration of a server may be examined using:
H A Dfpga_5gnr_fec.rst58 hugepage configuration of a server may be examined using:
H A Dfpga_lte_fec.rst57 hugepage configuration of a server may be examined using:
/dpdk/app/test/
H A Dmeson.build467 message('hugepage availability: @0@'.format(has_hugepage))
/dpdk/doc/guides/rel_notes/
H A Drelease_18_05.rst14 On Linux, support for reserving/unreserving hugepage memory at runtime has been
39 a mechanism guaranteeing minimum availability of hugepage memory to the
H A Drelease_22_03.rst14 It is now possible to reuse files in hugetlbfs to speed up hugepage mapping,
H A Drelease_19_02.rst16 hugepage allocations. A new ``--match-allocations`` EAL init flag has

12