476c847ab6
SPDK uses the rte_mem_event_callback_register API to create RDMA memory regions (MRs) for newly allocated regions of memory. This is used in both the SPDK NVMe-oF target and the NVMe-oF host driver. DPDK creates internal malloc_elem structures for these allocated regions. As users malloc and free memory, DPDK will sometimes merge malloc_elems that originated from different allocations that were notified through the registered mem_event callback routine. This results in subsequent allocations that can span across multiple RDMA MRs. This requires SPDK to check each DPDK buffer to see if it crosses an MR boundary, and if so, would have to add considerable logic and complexity to describe that buffer before it can be accessed by the RNIC. It is somewhat analagous to rte_malloc returning a buffer that is not IOVA-contiguous. As a malloc_elem gets split and some of these elements get freed, it can also result in DPDK sending an RTE_MEM_EVENT_FREE notification for a subset of the original RTE_MEM_EVENT_ALLOC notification. This is also problematic for RDMA memory regions, since unregistering the memory region is all-or-nothing. It is not possible to unregister part of a memory region. To support these types of applications, this patch adds a new --match-allocations EAL init flag. When this flag is specified, malloc elements from different hugepage allocations will never be merged. Memory will also only be freed back to the system (with the requisite memory event callback) exactly as it was originally allocated. Since part of this patch is extending the size of struct malloc_elem, we also fix up the malloc autotests so they do not assume its size exactly fits in one cacheline. Signed-off-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com>
123 lines
2.9 KiB
ReStructuredText
123 lines
2.9 KiB
ReStructuredText
.. SPDX-License-Identifier: BSD-3-Clause
|
|
Copyright(c) 2018 Intel Corporation.
|
|
|
|
EAL parameters
|
|
==============
|
|
|
|
This document contains a list of all EAL parameters. These parameters can be
|
|
used by any DPDK application running on Linux.
|
|
|
|
Common EAL parameters
|
|
---------------------
|
|
|
|
The following EAL parameters are common to all platforms supported by DPDK.
|
|
|
|
.. include:: eal_args.include.rst
|
|
|
|
Linux-specific EAL parameters
|
|
-----------------------------
|
|
|
|
In addition to common EAL parameters, there are also Linux-specific EAL
|
|
parameters.
|
|
|
|
Device-related options
|
|
~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ``--create-uio-dev``
|
|
|
|
Create ``/dev/uioX`` files for devices bound to igb_uio kernel driver
|
|
(usually done by the igb_uio driver itself).
|
|
|
|
* ``--vmware-tsc-map``
|
|
|
|
Use VMware TSC map instead of native RDTSC.
|
|
|
|
* ``--no-hpet``
|
|
|
|
Do not use the HPET timer.
|
|
|
|
* ``--vfio-intr <legacy|msi|msix>``
|
|
|
|
Use specified interrupt mode for devices bound to VFIO kernel driver.
|
|
|
|
Multiprocessing-related options
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ``--file-prefix <prefix name>``
|
|
|
|
Use a different shared data file prefix for a DPDK process. This option
|
|
allows running multiple independent DPDK primary/secondary processes under
|
|
different prefixes.
|
|
|
|
* ``--base-virtaddr <address>``
|
|
|
|
Attempt to use a different starting address for all memory maps of the
|
|
primary DPDK process. This can be helpful if secondary processes cannot
|
|
start due to conflicts in address map.
|
|
|
|
Memory-related options
|
|
~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
* ``--legacy-mem``
|
|
|
|
Use legacy DPDK memory allocation mode.
|
|
|
|
* ``--socket-mem <amounts of memory per socket>``
|
|
|
|
Preallocate specified amounts of memory per socket. The parameter is a
|
|
comma-separated list of values. For example::
|
|
|
|
--socket-mem 1024,2048
|
|
|
|
This will allocate 1 gigabyte of memory on socket 0, and 2048 megabytes of
|
|
memory on socket 1.
|
|
|
|
* ``--socket-limit <amounts of memory per socket>``
|
|
|
|
Place a per-socket upper limit on memory use (non-legacy memory mode only).
|
|
0 will disable the limit for a particular socket.
|
|
|
|
* ``--single-file-segments``
|
|
|
|
Create fewer files in hugetlbfs (non-legacy mode only).
|
|
|
|
* ``--huge-dir <path to hugetlbfs directory>``
|
|
|
|
Use specified hugetlbfs directory instead of autodetected ones.
|
|
|
|
* ``--huge-unlink``
|
|
|
|
Unlink hugepage files after creating them (implies no secondary process
|
|
support).
|
|
|
|
* ``--match-allocations``
|
|
|
|
Free hugepages back to system exactly as they were originally allocated.
|
|
|
|
Other options
|
|
~~~~~~~~~~~~~
|
|
|
|
* ``--syslog <syslog facility>``
|
|
|
|
Set syslog facility. Valid syslog facilities are::
|
|
|
|
auth
|
|
cron
|
|
daemon
|
|
ftp
|
|
kern
|
|
lpr
|
|
mail
|
|
news
|
|
syslog
|
|
user
|
|
uucp
|
|
local0
|
|
local1
|
|
local2
|
|
local3
|
|
local4
|
|
local5
|
|
local6
|
|
local7
|