Home
last modified time | relevance | path

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

12

/f-stack/app/redis-5.0.5/deps/jemalloc/test/unit/
H A Dpages.c6 void *pages, *hugepage; in TEST_BEGIN() local
14 hugepage = (void *)(ALIGNMENT_CEILING((uintptr_t)pages, HUGEPAGE)); in TEST_BEGIN()
15 assert_b_ne(pages_huge(hugepage, HUGEPAGE), have_madvise_huge, in TEST_BEGIN()
17 assert_false(pages_nohuge(hugepage, HUGEPAGE), in TEST_BEGIN()
/f-stack/dpdk/doc/guides/linux_gsg/
H A Dsys_reqs.rst153 By using hugepage allocations, performance is increased since fewer pages are needed,
197 For other hugepage sizes, for example 1G pages, the size must be specified explicitly and
198 can also be optionally set as the default hugepage size for the system.
199 For example, to reserve 4G of hugepage memory in the form of four 1G pages, the following options s…
205 … The hugepage sizes that a CPU supports can be determined from the CPU flags on Intel architecture.
207 On IBM Power architecture, the supported hugepage sizes are 16MB and 16GB.
230 This mount point will use the default hugepage size
233 However, in order to use hugepage sizes other than the default, it is necessary
234 to manually create mount points for those hugepage sizes (e.g. 1GB pages).
H A Dbuild_sample_apps.rst89 The prefix text used for hugepage filenames.
159 … also fail if the user requests less memory than the reserved amount of hugepage-memory, particula…
164 * 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 Dlinux_eal_parameters.rst88 Unlink hugepage files after creating them (implies no secondary process
H A Denable_func.rst71 * All directories which serve as hugepage mount points, for example, ``/dev/hugepages``
/f-stack/dpdk/lib/librte_eal/linux/
H A Deal_memory.c1112 struct hugepage_file *hugepage = NULL, *tmp_hp = NULL; local
1383 hugepage = create_shared_memory(eal_hugepage_data_path(),
1386 if (hugepage == NULL) {
1390 memset(hugepage, 0, nr_hugefiles * sizeof(struct hugepage_file));
1407 if (copy_hugepages_to_shared_mem(hugepage, nr_hugefiles,
1416 prealloc_segments(hugepage, nr_hugefiles)) {
1425 if (remap_needed_hugepages(hugepage, nr_hugefiles)) {
1441 munmap(hugepage, nr_hugefiles * sizeof(struct hugepage_file));
1442 hugepage = NULL;
1480 if (hugepage != NULL)
[all …]
/f-stack/doc/
H A DF-Stack_Quick_Start_Guide.md24 ## Set hugepage
35 Once the hugepage memory is reserved, to make the memory available for DPDK use, perform the follow…
H A DLaunch_F-Stack_on_AWS_EC2_in_one_minute.md17 # set hugepage
/f-stack/dpdk/doc/guides/nics/
H A Dbuild_and_test.rst44 hugepage size configured in the system and calculate the number of pages
55 Check ``/proc/meminfo`` to find system hugepage size:
H A Dvhost.rst95 Other basic DPDK preparations like hugepage enabling here.
H A Dvmxnet3.rst122 …Other instructions on preparing to use DPDK such as, hugepage enabling, uio port binding are not l…
/f-stack/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.
/f-stack/dpdk/doc/guides/tools/
H A Dhugepages.rst51 Select hugepage size to use.
/f-stack/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
169 hugepage memory will be preallocated.
197 All possible virtual memory space that can ever be used for hugepage mapping in
220 Preallocated virtual memory is not to be confused with preallocated hugepage
741 allocation from hugepage memory and to facilitate application porting.
835 previous and next elements. Due to the fact that hugepage memory can come and
/f-stack/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?
/f-stack/dpdk/app/test/
H A Dmeson.build443 has_hugepage = run_command('has-hugepage.sh').stdout().strip() != '0'
444 message('hugepage availability: @0@'.format(has_hugepage))
/f-stack/dpdk/doc/guides/freebsd_gsg/
H A Dbuild_sample_apps.rst95 The prefix text used for hugepage filenames.
/f-stack/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.
200 once the hugepage shared memory and the network ports are initialized,
300 …t the server process stores its port configuration data in a memory zone in hugepage shared memory.
/f-stack/app/redis-5.0.5/deps/jemalloc/
H A DINSTALL.md231 * `--with-lg-hugepage=<lg-hugepage>`
/f-stack/dpdk/doc/guides/bbdevs/
H A Dacc100.rst72 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:

12