1 .. SPDX-License-Identifier: BSD-3-Clause
2 Copyright 2015 6WIND S.A.
3 Copyright 2015 Mellanox Technologies, Ltd
5 .. include:: <isonum.txt>
10 The MLX5 poll mode driver library (**librte_net_mlx5**) provides support
11 for **Mellanox ConnectX-4**, **Mellanox ConnectX-4 Lx** , **Mellanox
12 ConnectX-5**, **Mellanox ConnectX-6**, **Mellanox ConnectX-6 Dx**, **Mellanox
13 ConnectX-6 Lx**, **Mellanox BlueField** and **Mellanox BlueField-2** families
14 of 10/25/40/50/100/200 Gb/s adapters as well as their virtual functions (VF)
17 Information and documentation about these adapters can be found on the
18 `Mellanox website <http://www.mellanox.com>`__. Help is also provided by the
19 `Mellanox community <http://community.mellanox.com/welcome>`__.
21 There is also a `section dedicated to this poll mode driver
22 <http://www.mellanox.com/page/products_dyn?product_family=209&mtag=pmd_for_dpdk>`__.
28 Besides its dependency on libibverbs (that implies libmlx5 and associated
29 kernel support), librte_net_mlx5 relies heavily on system calls for control
30 operations such as querying/updating the MTU and flow control parameters.
32 For security reasons and robustness, this driver only deals with virtual
33 memory addresses. The way resources allocations are handled by the kernel,
34 combined with hardware specifications that allow to handle virtual memory
35 addresses directly, ensure that DPDK applications cannot access random
36 physical memory (or memory that does not belong to the current process).
38 This capability allows the PMD to coexist with kernel network interfaces
39 which remain functional, although they stop receiving unicast packets as
40 long as they share the same MAC address.
41 This means legacy linux control tools (for example: ethtool, ifconfig and
42 more) can operate on the same network interfaces that owned by the DPDK
45 The PMD can use libibverbs and libmlx5 to access the device firmware
46 or directly the hardware components.
47 There are different levels of objects and bypassing abilities
48 to get the best performances:
50 - Verbs is a complete high-level generic API
51 - Direct Verbs is a device-specific API
52 - DevX allows to access firmware objects
53 - Direct Rules manages flow steering at low-level hardware layer
55 Enabling librte_net_mlx5 causes DPDK applications to be linked against
61 - Multi arch support: x86_64, POWER8, ARMv8, i686.
62 - Multiple TX and RX queues.
63 - Support for scattered TX frames.
64 - Advanced support for scattered Rx frames with tunable buffer attributes.
65 - IPv4, IPv6, TCPv4, TCPv6, UDPv4 and UDPv6 RSS on any number of queues.
66 - RSS using different combinations of fields: L3 only, L4 only or both,
67 and source only, destination only or both.
68 - Several RSS hash keys, one for each flow type.
69 - Default RSS operation with no hash key specification.
70 - Configurable RETA table.
71 - Link flow control (pause frame).
72 - Support for multiple MAC addresses.
76 - RX CRC stripping configuration.
77 - TX mbuf fast free offload.
78 - Promiscuous mode on PF and VF.
79 - Multicast promiscuous mode on PF and VF.
80 - Hardware checksum offloads.
81 - Flow director (RTE_FDIR_MODE_PERFECT, RTE_FDIR_MODE_PERFECT_MAC_VLAN and
83 - Flow API, including :ref:`flow_isolated_mode`.
85 - KVM and VMware ESX SR-IOV modes are supported.
86 - RSS hash result is supported.
87 - Hardware TSO for generic IP or UDP tunnel, including VXLAN and GRE.
88 - Hardware checksum Tx offload for generic IP or UDP tunnel, including VXLAN and GRE.
90 - Statistics query including Basic, Extended and per queue.
92 - Tunnel types: VXLAN, L3 VXLAN, VXLAN-GPE, GRE, MPLSoGRE, MPLSoUDP, IP-in-IP, Geneve, GTP.
93 - Tunnel HW offloads: packet type, inner/outer RSS, IP and UDP checksum verification.
94 - NIC HW offloads: encapsulation (vxlan, gre, mplsoudp, mplsogre), NAT, routing, TTL
95 increment/decrement, count, drop, mark. For details please see :ref:`mlx5_offloads_support`.
96 - Flow insertion rate of more then million flows per second, when using Direct Rules.
97 - Support for multiple rte_flow groups.
98 - Per packet no-inline hint flag to disable packet data copying into Tx descriptors.
101 - Multiple-thread flow insertion.
102 - Matching on IPv4 Internet Header Length (IHL).
103 - Matching on GTP extension header with raw encap/decap action.
104 - Matching on Geneve TLV option header with raw encap/decap action.
105 - RSS support in sample action.
106 - E-Switch mirroring and jump.
107 - E-Switch mirroring and modify.
108 - 21844 flow priorities for ingress or egress flow groups greater than 0 and for any transfer
110 - Flow metering, including meter policy API.
111 - Flow meter hierarchy.
112 - Flow integrity offload API.
113 - Connection tracking.
114 - Sub-Function representors.
123 On Windows, the features are limited:
125 - Promiscuous mode is not supported
126 - The following rules are supported:
128 - IPv4/UDP with CVLAN filtering
129 - Unicast MAC filtering
131 - Additional rules are supported from WinOF2 version 2.70:
133 - IPv4/TCP with CVLAN filtering
134 - L4 steering rules for port RSS of UDP, TCP and IP
136 - For secondary process:
138 - Forked secondary process not supported.
139 - External memory unregistered in EAL memseg list cannot be used for DMA
140 unless such memory has been registered by ``mlx5_mr_update_ext_mp()`` in
141 primary process and remapped to the same virtual address in secondary
142 process. If the external memory is registered by primary process but has
143 different virtual address in secondary process, unexpected error may happen.
145 - When using Verbs flow engine (``dv_flow_en`` = 0), flow pattern without any
146 specific VLAN will match for VLAN packets as well:
148 When VLAN spec is not specified in the pattern, the matching rule will be created with VLAN as a wild card.
149 Meaning, the flow rule::
151 flow create 0 ingress pattern eth / vlan vid is 3 / ipv4 / end ...
153 Will only match vlan packets with vid=3. and the flow rule::
155 flow create 0 ingress pattern eth / ipv4 / end ...
157 Will match any ipv4 packet (VLAN included).
159 - When using Verbs flow engine (``dv_flow_en`` = 0), multi-tagged(QinQ) match is not supported.
161 - When using DV flow engine (``dv_flow_en`` = 1), flow pattern with any VLAN specification will match only single-tagged packets unless the ETH item ``type`` field is 0x88A8 or the VLAN item ``has_more_vlan`` field is 1.
164 flow create 0 ingress pattern eth / ipv4 / end ...
166 Will match any ipv4 packet.
169 flow create 0 ingress pattern eth / vlan / end ...
170 flow create 0 ingress pattern eth has_vlan is 1 / end ...
171 flow create 0 ingress pattern eth type is 0x8100 / end ...
173 Will match single-tagged packets only, with any VLAN ID value.
176 flow create 0 ingress pattern eth type is 0x88A8 / end ...
177 flow create 0 ingress pattern eth / vlan has_more_vlan is 1 / end ...
179 Will match multi-tagged packets only, with any VLAN ID value.
181 - A flow pattern with 2 sequential VLAN items is not supported.
183 - VLAN pop offload command:
185 - Flow rules having a VLAN pop offload command as one of their actions and
186 are lacking a match on VLAN as one of their items are not supported.
187 - The command is not supported on egress traffic in NIC mode.
189 - VLAN push offload is not supported on ingress traffic in NIC mode.
191 - VLAN set PCP offload is not supported on existing headers.
193 - A multi segment packet must have not more segments than reported by dev_infos_get()
194 in tx_desc_lim.nb_seg_max field. This value depends on maximal supported Tx descriptor
195 size and ``txq_inline_min`` settings and may be from 2 (worst case forced by maximal
196 inline settings) to 58.
198 - Match on VXLAN supports the following fields only:
201 - Last reserved 8-bits
203 Last reserved 8-bits matching is only supported When using DV flow
204 engine (``dv_flow_en`` = 1).
205 For ConnectX-5, the UDP destination port must be the standard one (4789).
206 Group zero's behavior may differ which depends on FW.
207 Matching value equals 0 (value & mask) is not supported.
209 - L3 VXLAN and VXLAN-GPE tunnels cannot be supported together with MPLSoGRE and MPLSoUDP.
211 - Match on Geneve header supports the following fields only:
218 - Match on Geneve TLV option is supported on the following fields:
225 Only one Class/Type/Length Geneve TLV option is supported per shared device.
226 Class/Type/Length fields must be specified as well as masks.
227 Class/Type/Length specified masks must be full.
228 Matching Geneve TLV option without specifying data is not supported.
229 Matching Geneve TLV option with ``data & mask == 0`` is not supported.
231 - VF: flow rules created on VF devices can only match traffic targeted at the
232 configured MAC addresses (see ``rte_eth_dev_mac_addr_add()``).
234 - Match on GTP tunnel header item supports the following fields only:
236 - v_pt_rsv_flags: E flag, S flag, PN flag
240 - Match on GTP extension header only for GTP PDU session container (next
241 extension header type = 0x85).
242 - Match on GTP extension header is not supported in group 0.
244 - No Tx metadata go to the E-Switch steering domain for the Flow group 0.
245 The flows within group 0 and set metadata action are rejected by hardware.
249 MAC addresses not already present in the bridge table of the associated
250 kernel network device will be added and cleaned up by the PMD when closing
251 the device. In case of ungraceful program termination, some entries may
252 remain present and should be removed manually by other means.
254 - Buffer split offload is supported with regular Rx burst routine only,
255 no MPRQ feature or vectorized code can be engaged.
257 - When Multi-Packet Rx queue is configured (``mprq_en``), a Rx packet can be
258 externally attached to a user-provided mbuf with having RTE_MBUF_F_EXTERNAL in
259 ol_flags. As the mempool for the external buffer is managed by PMD, all the
260 Rx mbufs must be freed before the device is closed. Otherwise, the mempool of
261 the external buffers will be freed by PMD and the application which still
262 holds the external buffers may be corrupted.
264 - If Multi-Packet Rx queue is configured (``mprq_en``) and Rx CQE compression is
265 enabled (``rxq_cqe_comp_en``) at the same time, RSS hash result is not fully
266 supported. Some Rx packets may not have RTE_MBUF_F_RX_RSS_HASH.
268 - IPv6 Multicast messages are not supported on VM, while promiscuous mode
269 and allmulticast mode are both set to off.
270 To receive IPv6 Multicast messages on VM, explicitly set the relevant
271 MAC address using rte_eth_dev_mac_addr_add() API.
273 - To support a mixed traffic pattern (some buffers from local host memory, some
274 buffers from other devices) with high bandwidth, a mbuf flag is used.
276 An application hints the PMD whether or not it should try to inline the
277 given mbuf data buffer. PMD should do the best effort to act upon this request.
279 The hint flag ``RTE_PMD_MLX5_FINE_GRANULARITY_INLINE`` is dynamic,
280 registered by application with rte_mbuf_dynflag_register(). This flag is
281 purely driver-specific and declared in PMD specific header ``rte_pmd_mlx5.h``,
282 which is intended to be used by the application.
284 To query the supported specific flags in runtime,
285 the function ``rte_pmd_mlx5_get_dyn_flag_names`` returns the array of
286 currently (over present hardware and configuration) supported specific flags.
287 The "not inline hint" feature operating flow is the following one:
290 - probe the devices, ports are created
291 - query the port capabilities
292 - if port supporting the feature is found
293 - register dynamic flag ``RTE_PMD_MLX5_FINE_GRANULARITY_INLINE``
294 - application starts the ports
295 - on ``dev_start()`` PMD checks whether the feature flag is registered and
296 enables the feature support in datapath
297 - application might set the registered flag bit in ``ol_flags`` field
298 of mbuf being sent and PMD will handle ones appropriately.
300 - The amount of descriptors in Tx queue may be limited by data inline settings.
301 Inline data require the more descriptor building blocks and overall block
302 amount may exceed the hardware supported limits. The application should
303 reduce the requested Tx size or adjust data inline settings with
304 ``txq_inline_max`` and ``txq_inline_mpw`` devargs keys.
306 - To provide the packet send scheduling on mbuf timestamps the ``tx_pp``
307 parameter should be specified.
308 When PMD sees the RTE_MBUF_DYNFLAG_TX_TIMESTAMP_NAME set on the packet
309 being sent it tries to synchronize the time of packet appearing on
310 the wire with the specified packet timestamp. It the specified one
311 is in the past it should be ignored, if one is in the distant future
312 it should be capped with some reasonable value (in range of seconds).
313 These specific cases ("too late" and "distant future") can be optionally
314 reported via device xstats to assist applications to detect the
315 time-related problems.
317 The timestamp upper "too-distant-future" limit
318 at the moment of invoking the Tx burst routine
319 can be estimated as ``tx_pp`` option (in nanoseconds) multiplied by 2^23.
320 Please note, for the testpmd txonly mode,
321 the limit is deduced from the expression::
323 (n_tx_descriptors / burst_size + 1) * inter_burst_gap
325 There is no any packet reordering according timestamps is supposed,
326 neither within packet burst, nor between packets, it is an entirely
327 application responsibility to generate packets and its timestamps
328 in desired order. The timestamps can be put only in the first packet
329 in the burst providing the entire burst scheduling.
331 - E-Switch decapsulation Flow:
333 - can be applied to PF port only.
334 - must specify VF port action (packet redirection from PF to VF).
335 - optionally may specify tunnel inner source and destination MAC addresses.
337 - E-Switch encapsulation Flow:
339 - can be applied to VF ports only.
340 - must specify PF port action (packet redirection from VF to PF).
344 - The input buffer, used as outer header, is not validated.
348 - The decapsulation is always done up to the outermost tunnel detected by the HW.
349 - The input buffer, providing the removal size, is not validated.
350 - The buffer size must match the length of the headers to be removed.
352 - ICMP(code/type/identifier/sequence number) / ICMP6(code/type) matching, IP-in-IP and MPLS flow matching are all
353 mutually exclusive features which cannot be supported together
354 (see :ref:`mlx5_firmware_config`).
358 - Requires DevX and DV flow to be enabled.
359 - KEEP_CRC offload cannot be supported with LRO.
360 - The first mbuf length, without head-room, must be big enough to include the
362 - Rx queue with LRO offload enabled, receiving a non-LRO packet, can forward
363 it with size limited to max LRO size, not to max RX packet length.
364 - LRO can be used with outer header of TCP packets of the standard format:
365 eth (with or without vlan) / ipv4 or ipv6 / tcp / payload
367 Other TCP packets (e.g. with MPLS label) received on Rx queue with LRO enabled, will be received with bad checksum.
368 - LRO packet aggregation is performed by HW only for packet size larger than
369 ``lro_min_mss_size``. This value is reported on device start, when debug
374 - ``RTE_ETH_RX_OFFLOAD_KEEP_CRC`` cannot be supported with decapsulation
375 for some NICs (such as ConnectX-6 Dx, ConnectX-6 Lx, and BlueField-2).
376 The capability bit ``scatter_fcs_w_decap_disable`` shows NIC support.
380 - fast free offload assumes the all mbufs being sent are originated from the
381 same memory pool and there is no any extra references to the mbufs (the
382 reference counter for each mbuf is equal 1 on tx_burst call). The latter
383 means there should be no any externally attached buffers in mbufs. It is
384 an application responsibility to provide the correct mbufs if the fast
385 free offload is engaged. The mlx5 PMD implicitly produces the mbufs with
386 externally attached buffers if MPRQ option is enabled, hence, the fast
387 free offload is neither supported nor advertised if there is MPRQ enabled.
391 - Supports ``RTE_FLOW_ACTION_TYPE_SAMPLE`` action only within NIC Rx and
392 E-Switch steering domain.
393 - For E-Switch Sampling flow with sample ratio > 1, additional actions are not
394 supported in the sample actions list.
395 - For ConnectX-5, the ``RTE_FLOW_ACTION_TYPE_SAMPLE`` is typically used as
396 first action in the E-Switch egress flow if with header modify or
397 encapsulation actions.
398 - For NIC Rx flow, supports ``MARK``, ``COUNT``, ``QUEUE``, ``RSS`` in the
400 - For E-Switch mirroring flow, supports ``RAW ENCAP``, ``Port ID``,
401 ``VXLAN ENCAP``, ``NVGRE ENCAP`` in the sample actions list.
405 - Supports the 'set' operation only for ``RTE_FLOW_ACTION_TYPE_MODIFY_FIELD`` action.
406 - Modification of an arbitrary place in a packet via the special ``RTE_FLOW_FIELD_START`` Field ID is not supported.
407 - Modification of the 802.1Q Tag, VXLAN Network or GENEVE Network ID's is not supported.
408 - Encapsulation levels are not supported, can modify outermost header fields only.
409 - Offsets must be 32-bits aligned, cannot skip past the boundary of a field.
411 - IPv6 header item 'proto' field, indicating the next header protocol, should
412 not be set as extension header.
413 In case the next header is an extension header, it should not be specified in
414 IPv6 header item 'proto' field.
415 The last extension header item 'next header' field can specify the following
416 header protocol type.
420 - Hairpin between two ports could only manual binding and explicit Tx flow mode. For single port hairpin, all the combinations of auto/manual binding and explicit/implicit Tx flow mode could be supported.
421 - Hairpin in switchdev SR-IOV mode is not supported till now.
425 - All the meter colors with drop action will be counted only by the global drop statistics.
426 - Yellow detection is only supported with ASO metering.
427 - Red color must be with drop action.
428 - Meter statistics are supported only for drop case.
429 - A meter action created with pre-defined policy must be the last action in the flow except single case where the policy actions are:
430 - green: NULL or END.
431 - yellow: NULL or END.
433 - The only supported meter policy actions:
434 - green: QUEUE, RSS, PORT_ID, REPRESENTED_PORT, JUMP, DROP, MARK and SET_TAG.
435 - yellow: QUEUE, RSS, PORT_ID, REPRESENTED_PORT, JUMP, DROP, MARK and SET_TAG.
437 - Policy actions of RSS for green and yellow should have the same configuration except queues.
438 - Policy with RSS/queue action is not supported when ``dv_xmeta_en`` enabled.
439 - meter profile packet mode is supported.
440 - meter profiles of RFC2697, RFC2698 and RFC4115 are supported.
444 - Integrity offload is enabled for **ConnectX-6** family.
445 - Verification bits provided by the hardware are ``l3_ok``, ``ipv4_csum_ok``, ``l4_ok``, ``l4_csum_ok``.
446 - ``level`` value 0 references outer headers.
447 - Multiple integrity items not supported in a single flow rule.
448 - Flow rule items supplied by application must explicitly specify network headers referred by integrity item.
449 For example, if integrity item mask sets ``l4_ok`` or ``l4_csum_ok`` bits, reference to L4 network header,
450 TCP or UDP, must be in the rule pattern as well::
452 flow create 0 ingress pattern integrity level is 0 value mask l3_ok value spec l3_ok / eth / ipv6 / end …
454 flow create 0 ingress pattern integrity level is 0 value mask l4_ok value spec 0 / eth / ipv4 proto is udp / end …
456 - Connection tracking:
458 - Cannot co-exist with ASO meter, ASO age action in a single flow rule.
459 - Flow rules insertion rate and memory consumption need more optimization.
461 - 4M connections maximum.
463 - Multi-thread flow insertion:
465 - In order to achieve best insertion rate, application should manage the flows per lcore.
466 - Better to disable memory reclaim by setting ``reclaim_mem_mode`` to 0 to accelerate the flow object allocation and release with cache.
470 - TXQ affinity subjects to HW hash once enabled.
472 - Bonding under socket direct mode
479 MLX5 supports various methods to report statistics:
481 Port statistics can be queried using ``rte_eth_stats_get()``. The received and sent statistics are through SW only and counts the number of packets received or sent successfully by the PMD. The imissed counter is the amount of packets that could not be delivered to SW because a queue was full. Packets not received due to congestion in the bus or on the NIC can be queried via the rx_discards_phy xstats counter.
483 Extended statistics can be queried using ``rte_eth_xstats_get()``. The extended statistics expose a wider set of counters counted by the device. The extended port statistics counts the number of packets received or sent successfully by the port. As Mellanox NICs are using the :ref:`Bifurcated Linux Driver <linux_gsg_linux_drivers>` those counters counts also packet received or sent by the Linux kernel. The counters with ``_phy`` suffix counts the total events on the physical port, therefore not valid for VF.
485 Finally per-flow statistics can by queried using ``rte_flow_query`` when attaching a count action for specific flow. The flow counter counts the number of packets received successfully by the port and match the specific flow.
493 The ibverbs libraries can be linked with this PMD in a number of ways,
494 configured by the ``ibverbs_link`` build option:
496 - ``shared`` (default): the PMD depends on some .so files.
498 - ``dlopen``: Split the dependencies glue in a separate library
499 loaded when needed by dlopen.
500 It make dependencies on libibverbs and libmlx4 optional,
501 and has no performance impact.
503 - ``static``: Embed static flavor of the dependencies libibverbs and libmlx4
504 in the PMD shared library or the executable static binary.
506 Environment variables
507 ~~~~~~~~~~~~~~~~~~~~~
511 A list of directories in which to search for the rdma-core "glue" plug-in,
512 separated by colons or semi-colons.
514 - ``MLX5_SHUT_UP_BF``
516 Configures HW Tx doorbell register as IO-mapped.
518 By default, the HW Tx doorbell is configured as a write-combining register.
519 The register would be flushed to HW usually when the write-combining buffer
520 becomes full, but it depends on CPU design.
522 Except for vectorized Tx burst routines, a write memory barrier is enforced
523 after updating the register so that the update can be immediately visible to
526 When vectorized Tx burst is called, the barrier is set only if the burst size
527 is not aligned to MLX5_VPMD_TX_MAX_BURST. However, setting this environmental
528 variable will bring better latency even though the maximum throughput can
531 Run-time configuration
532 ~~~~~~~~~~~~~~~~~~~~~~
534 - librte_net_mlx5 brings kernel network interfaces up during initialization
535 because it is affected by their state. Forcing them down prevents packets
538 - **ethtool** operations on related kernel interfaces also affect the PMD.
543 In order to run as a non-root user,
544 some capabilities must be granted to the application::
546 setcap cap_sys_admin,cap_net_admin,cap_net_raw,cap_ipc_lock+ep <dpdk-app>
548 Below are the reasons of the need for each capability:
551 When using physical addresses (PA mode), with Linux >= 4.0,
552 for access to ``/proc/self/pagemap``.
555 For device configuration.
558 For raw ethernet queue allocation through kernel driver.
561 For DMA memory pinning.
566 - ``rxq_cqe_comp_en`` parameter [int]
568 A nonzero value enables the compression of CQE on RX side. This feature
569 allows to save PCI bandwidth and improve performance. Enabled by default.
570 Different compression formats are supported in order to achieve the best
571 performance for different traffic patterns. Default format depends on
572 Multi-Packet Rx queue configuration: Hash RSS format is used in case
573 MPRQ is disabled, Checksum format is used in case MPRQ is enabled.
575 Specifying 2 as a ``rxq_cqe_comp_en`` value selects Flow Tag format for
576 better compression rate in case of RTE Flow Mark traffic.
577 Specifying 3 as a ``rxq_cqe_comp_en`` value selects Checksum format.
578 Specifying 4 as a ``rxq_cqe_comp_en`` value selects L3/L4 Header format for
579 better compression rate in case of mixed TCP/UDP and IPv4/IPv6 traffic.
580 CQE compression format selection requires DevX to be enabled. If there is
581 no DevX enabled/supported the value is reset to 1 by default.
585 - x86_64 with ConnectX-4, ConnectX-4 Lx, ConnectX-5, ConnectX-6, ConnectX-6 Dx,
586 ConnectX-6 Lx, BlueField and BlueField-2.
587 - POWER9 and ARMv8 with ConnectX-4 Lx, ConnectX-5, ConnectX-6, ConnectX-6 Dx,
588 ConnectX-6 Lx, BlueField and BlueField-2.
590 - ``rxq_pkt_pad_en`` parameter [int]
592 A nonzero value enables padding Rx packet to the size of cacheline on PCI
593 transaction. This feature would waste PCI bandwidth but could improve
594 performance by avoiding partial cacheline write which may cause costly
595 read-modify-copy in memory transaction on some architectures. Disabled by
600 - x86_64 with ConnectX-4, ConnectX-4 Lx, ConnectX-5, ConnectX-6, ConnectX-6 Dx,
601 ConnectX-6 Lx, BlueField and BlueField-2.
602 - POWER8 and ARMv8 with ConnectX-4 Lx, ConnectX-5, ConnectX-6, ConnectX-6 Dx,
603 ConnectX-6 Lx, BlueField and BlueField-2.
605 - ``mprq_en`` parameter [int]
607 A nonzero value enables configuring Multi-Packet Rx queues. Rx queue is
608 configured as Multi-Packet RQ if the total number of Rx queues is
609 ``rxqs_min_mprq`` or more. Disabled by default.
611 Multi-Packet Rx Queue (MPRQ a.k.a Striding RQ) can further save PCIe bandwidth
612 by posting a single large buffer for multiple packets. Instead of posting a
613 buffers per a packet, one large buffer is posted in order to receive multiple
614 packets on the buffer. A MPRQ buffer consists of multiple fixed-size strides
615 and each stride receives one packet. MPRQ can improve throughput for
616 small-packet traffic.
618 When MPRQ is enabled, MTU can be larger than the size of
619 user-provided mbuf even if RTE_ETH_RX_OFFLOAD_SCATTER isn't enabled. PMD will
620 configure large stride size enough to accommodate MTU as long as
621 device allows. Note that this can waste system memory compared to enabling Rx
622 scatter and multi-segment packet.
624 - ``mprq_log_stride_num`` parameter [int]
626 Log 2 of the number of strides for Multi-Packet Rx queue. Configuring more
627 strides can reduce PCIe traffic further. If configured value is not in the
628 range of device capability, the default value will be set with a warning
629 message. The default value is 4 which is 16 strides per a buffer, valid only
630 if ``mprq_en`` is set.
632 The size of Rx queue should be bigger than the number of strides.
634 - ``mprq_log_stride_size`` parameter [int]
636 Log 2 of the size of a stride for Multi-Packet Rx queue. Configuring a smaller
637 stride size can save some memory and reduce probability of a depletion of all
638 available strides due to unreleased packets by an application. If configured
639 value is not in the range of device capability, the default value will be set
640 with a warning message. The default value is 11 which is 2048 bytes per a
641 stride, valid only if ``mprq_en`` is set. With ``mprq_log_stride_size`` set
642 it is possible for a packet to span across multiple strides. This mode allows
643 support of jumbo frames (9K) with MPRQ. The memcopy of some packets (or part
644 of a packet if Rx scatter is configured) may be required in case there is no
645 space left for a head room at the end of a stride which incurs some
648 - ``mprq_max_memcpy_len`` parameter [int]
650 The maximum length of packet to memcpy in case of Multi-Packet Rx queue. Rx
651 packet is mem-copied to a user-provided mbuf if the size of Rx packet is less
652 than or equal to this parameter. Otherwise, PMD will attach the Rx packet to
653 the mbuf by external buffer attachment - ``rte_pktmbuf_attach_extbuf()``.
654 A mempool for external buffers will be allocated and managed by PMD. If Rx
655 packet is externally attached, ol_flags field of the mbuf will have
656 RTE_MBUF_F_EXTERNAL and this flag must be preserved. ``RTE_MBUF_HAS_EXTBUF()``
657 checks the flag. The default value is 128, valid only if ``mprq_en`` is set.
659 - ``rxqs_min_mprq`` parameter [int]
661 Configure Rx queues as Multi-Packet RQ if the total number of Rx queues is
662 greater or equal to this value. The default value is 12, valid only if
665 - ``txq_inline`` parameter [int]
667 Amount of data to be inlined during TX operations. This parameter is
668 deprecated and converted to the new parameter ``txq_inline_max`` providing
669 partial compatibility.
671 - ``txqs_min_inline`` parameter [int]
673 Enable inline data send only when the number of TX queues is greater or equal
676 This option should be used in combination with ``txq_inline_max`` and
677 ``txq_inline_mpw`` below and does not affect ``txq_inline_min`` settings above.
679 If this option is not specified the default value 16 is used for BlueField
680 and 8 for other platforms
682 The data inlining consumes the CPU cycles, so this option is intended to
683 auto enable inline data if we have enough Tx queues, which means we have
684 enough CPU cores and PCI bandwidth is getting more critical and CPU
685 is not supposed to be bottleneck anymore.
687 The copying data into WQE improves latency and can improve PPS performance
688 when PCI back pressure is detected and may be useful for scenarios involving
689 heavy traffic on many queues.
691 Because additional software logic is necessary to handle this mode, this
692 option should be used with care, as it may lower performance when back
693 pressure is not expected.
695 If inline data are enabled it may affect the maximal size of Tx queue in
696 descriptors because the inline data increase the descriptor size and
697 queue size limits supported by hardware may be exceeded.
699 - ``txq_inline_min`` parameter [int]
701 Minimal amount of data to be inlined into WQE during Tx operations. NICs
702 may require this minimal data amount to operate correctly. The exact value
703 may depend on NIC operation mode, requested offloads, etc. It is strongly
704 recommended to omit this parameter and use the default values. Anyway,
705 applications using this parameter should take into consideration that
706 specifying an inconsistent value may prevent the NIC from sending packets.
708 If ``txq_inline_min`` key is present the specified value (may be aligned
709 by the driver in order not to exceed the limits and provide better descriptor
710 space utilization) will be used by the driver and it is guaranteed that
711 requested amount of data bytes are inlined into the WQE beside other inline
712 settings. This key also may update ``txq_inline_max`` value (default
713 or specified explicitly in devargs) to reserve the space for inline data.
715 If ``txq_inline_min`` key is not present, the value may be queried by the
716 driver from the NIC via DevX if this feature is available. If there is no DevX
717 enabled/supported the value 18 (supposing L2 header including VLAN) is set
718 for ConnectX-4 and ConnectX-4 Lx, and 0 is set by default for ConnectX-5
719 and newer NICs. If packet is shorter the ``txq_inline_min`` value, the entire
722 For ConnectX-4 NIC, driver does not allow specifying value below 18
723 (minimal L2 header, including VLAN), error will be raised.
725 For ConnectX-4 Lx NIC, it is allowed to specify values below 18, but
726 it is not recommended and may prevent NIC from sending packets over
729 For ConnectX-4 and ConnectX-4 Lx NICs, automatically configured value
730 is insufficient for some traffic, because they require at least all L2 headers
731 to be inlined. For example, Q-in-Q adds 4 bytes to default 18 bytes
732 of Ethernet and VLAN, thus ``txq_inline_min`` must be set to 22.
733 MPLS would add 4 bytes per label. Final value must account for all possible
734 L2 encapsulation headers used in particular environment.
736 Please, note, this minimal data inlining disengages eMPW feature (Enhanced
737 Multi-Packet Write), because last one does not support partial packet inlining.
738 This is not very critical due to minimal data inlining is mostly required
739 by ConnectX-4 and ConnectX-4 Lx, these NICs do not support eMPW feature.
741 - ``txq_inline_max`` parameter [int]
743 Specifies the maximal packet length to be completely inlined into WQE
744 Ethernet Segment for ordinary SEND method. If packet is larger than specified
745 value, the packet data won't be copied by the driver at all, data buffer
746 is addressed with a pointer. If packet length is less or equal all packet
747 data will be copied into WQE. This may improve PCI bandwidth utilization for
748 short packets significantly but requires the extra CPU cycles.
750 The data inline feature is controlled by number of Tx queues, if number of Tx
751 queues is larger than ``txqs_min_inline`` key parameter, the inline feature
752 is engaged, if there are not enough Tx queues (which means not enough CPU cores
753 and CPU resources are scarce), data inline is not performed by the driver.
754 Assigning ``txqs_min_inline`` with zero always enables the data inline.
756 The default ``txq_inline_max`` value is 290. The specified value may be adjusted
757 by the driver in order not to exceed the limit (930 bytes) and to provide better
758 WQE space filling without gaps, the adjustment is reflected in the debug log.
759 Also, the default value (290) may be decreased in run-time if the large transmit
760 queue size is requested and hardware does not support enough descriptor
761 amount, in this case warning is emitted. If ``txq_inline_max`` key is
762 specified and requested inline settings can not be satisfied then error
765 - ``txq_inline_mpw`` parameter [int]
767 Specifies the maximal packet length to be completely inlined into WQE for
768 Enhanced MPW method. If packet is large the specified value, the packet data
769 won't be copied, and data buffer is addressed with pointer. If packet length
770 is less or equal, all packet data will be copied into WQE. This may improve PCI
771 bandwidth utilization for short packets significantly but requires the extra
774 The data inline feature is controlled by number of TX queues, if number of Tx
775 queues is larger than ``txqs_min_inline`` key parameter, the inline feature
776 is engaged, if there are not enough Tx queues (which means not enough CPU cores
777 and CPU resources are scarce), data inline is not performed by the driver.
778 Assigning ``txqs_min_inline`` with zero always enables the data inline.
780 The default ``txq_inline_mpw`` value is 268. The specified value may be adjusted
781 by the driver in order not to exceed the limit (930 bytes) and to provide better
782 WQE space filling without gaps, the adjustment is reflected in the debug log.
783 Due to multiple packets may be included to the same WQE with Enhanced Multi
784 Packet Write Method and overall WQE size is limited it is not recommended to
785 specify large values for the ``txq_inline_mpw``. Also, the default value (268)
786 may be decreased in run-time if the large transmit queue size is requested
787 and hardware does not support enough descriptor amount, in this case warning
788 is emitted. If ``txq_inline_mpw`` key is specified and requested inline
789 settings can not be satisfied then error will be raised.
791 - ``txqs_max_vec`` parameter [int]
793 Enable vectorized Tx only when the number of TX queues is less than or
794 equal to this value. This parameter is deprecated and ignored, kept
795 for compatibility issue to not prevent driver from probing.
797 - ``txq_mpw_hdr_dseg_en`` parameter [int]
799 A nonzero value enables including two pointers in the first block of TX
800 descriptor. The parameter is deprecated and ignored, kept for compatibility
803 - ``txq_max_inline_len`` parameter [int]
805 Maximum size of packet to be inlined. This limits the size of packet to
806 be inlined. If the size of a packet is larger than configured value, the
807 packet isn't inlined even though there's enough space remained in the
808 descriptor. Instead, the packet is included with pointer. This parameter
809 is deprecated and converted directly to ``txq_inline_mpw`` providing full
810 compatibility. Valid only if eMPW feature is engaged.
812 - ``txq_mpw_en`` parameter [int]
814 A nonzero value enables Enhanced Multi-Packet Write (eMPW) for ConnectX-5,
815 ConnectX-6, ConnectX-6 Dx, ConnectX-6 Lx, BlueField, BlueField-2.
816 eMPW allows the Tx burst function to pack up multiple packets
817 in a single descriptor session in order to save PCI bandwidth
818 and improve performance at the cost of a slightly higher CPU usage.
819 When ``txq_inline_mpw`` is set along with ``txq_mpw_en``,
820 Tx burst function copies entire packet data on to Tx descriptor
821 instead of including pointer of packet.
823 The Enhanced Multi-Packet Write feature is enabled by default if NIC supports
824 it, can be disabled by explicit specifying 0 value for ``txq_mpw_en`` option.
825 Also, if minimal data inlining is requested by non-zero ``txq_inline_min``
826 option or reported by the NIC, the eMPW feature is disengaged.
828 - ``tx_db_nc`` parameter [int]
830 The rdma core library can map doorbell register in two ways, depending on the
831 environment variable "MLX5_SHUT_UP_BF":
833 - As regular cached memory (usually with write combining attribute), if the
834 variable is either missing or set to zero.
835 - As non-cached memory, if the variable is present and set to not "0" value.
837 The type of mapping may slightly affect the Tx performance, the optimal choice
838 is strongly relied on the host architecture and should be deduced practically.
840 If ``tx_db_nc`` is set to zero, the doorbell is forced to be mapped to regular
841 memory (with write combining), the PMD will perform the extra write memory barrier
842 after writing to doorbell, it might increase the needed CPU clocks per packet
843 to send, but latency might be improved.
845 If ``tx_db_nc`` is set to one, the doorbell is forced to be mapped to non
846 cached memory, the PMD will not perform the extra write memory barrier
847 after writing to doorbell, on some architectures it might improve the
850 If ``tx_db_nc`` is set to two, the doorbell is forced to be mapped to regular
851 memory, the PMD will use heuristics to decide whether write memory barrier
852 should be performed. For bursts with size multiple of recommended one (64 pkts)
853 it is supposed the next burst is coming and no need to issue the extra memory
854 barrier (it is supposed to be issued in the next coming burst, at least after
855 descriptor writing). It might increase latency (on some hosts till next
856 packets transmit) and should be used with care.
858 If ``tx_db_nc`` is omitted or set to zero, the preset (if any) environment
859 variable "MLX5_SHUT_UP_BF" value is used. If there is no "MLX5_SHUT_UP_BF",
860 the default ``tx_db_nc`` value is zero for ARM64 hosts and one for others.
862 - ``tx_pp`` parameter [int]
864 If a nonzero value is specified the driver creates all necessary internal
865 objects to provide accurate packet send scheduling on mbuf timestamps.
866 The positive value specifies the scheduling granularity in nanoseconds,
867 the packet send will be accurate up to specified digits. The allowed range is
868 from 500 to 1 million of nanoseconds. The negative value specifies the module
869 of granularity and engages the special test mode the check the schedule rate.
870 By default (if the ``tx_pp`` is not specified) send scheduling on timestamps
873 - ``tx_skew`` parameter [int]
875 The parameter adjusts the send packet scheduling on timestamps and represents
876 the average delay between beginning of the transmitting descriptor processing
877 by the hardware and appearance of actual packet data on the wire. The value
878 should be provided in nanoseconds and is valid only if ``tx_pp`` parameter is
879 specified. The default value is zero.
881 - ``tx_vec_en`` parameter [int]
883 A nonzero value enables Tx vector on ConnectX-5, ConnectX-6, ConnectX-6 Dx,
884 ConnectX-6 Lx, BlueField and BlueField-2 NICs
885 if the number of global Tx queues on the port is less than ``txqs_max_vec``.
886 The parameter is deprecated and ignored.
888 - ``rx_vec_en`` parameter [int]
890 A nonzero value enables Rx vector if the port is not configured in
891 multi-segment otherwise this parameter is ignored.
895 - ``vf_nl_en`` parameter [int]
897 A nonzero value enables Netlink requests from the VF to add/remove MAC
898 addresses or/and enable/disable promiscuous/all multicast on the Netdevice.
899 Otherwise the relevant configuration must be run with Linux iproute2 tools.
900 This is a prerequisite to receive this kind of traffic.
902 Enabled by default, valid only on VF devices ignored otherwise.
904 - ``l3_vxlan_en`` parameter [int]
906 A nonzero value allows L3 VXLAN and VXLAN-GPE flow creation. To enable
907 L3 VXLAN or VXLAN-GPE, users has to configure firmware and enable this
908 parameter. This is a prerequisite to receive this kind of traffic.
912 - ``dv_xmeta_en`` parameter [int]
914 A nonzero value enables extensive flow metadata support if device is
915 capable and driver supports it. This can enable extensive support of
916 ``MARK`` and ``META`` item of ``rte_flow``. The newly introduced
917 ``SET_TAG`` and ``SET_META`` actions do not depend on ``dv_xmeta_en``.
919 There are some possible configurations, depending on parameter value:
921 - 0, this is default value, defines the legacy mode, the ``MARK`` and
922 ``META`` related actions and items operate only within NIC Tx and
923 NIC Rx steering domains, no ``MARK`` and ``META`` information crosses
924 the domain boundaries. The ``MARK`` item is 24 bits wide, the ``META``
925 item is 32 bits wide and match supported on egress only.
927 - 1, this engages extensive metadata mode, the ``MARK`` and ``META``
928 related actions and items operate within all supported steering domains,
929 including FDB, ``MARK`` and ``META`` information may cross the domain
930 boundaries. The ``MARK`` item is 24 bits wide, the ``META`` item width
931 depends on kernel and firmware configurations and might be 0, 16 or
932 32 bits. Within NIC Tx domain ``META`` data width is 32 bits for
933 compatibility, the actual width of data transferred to the FDB domain
934 depends on kernel configuration and may be vary. The actual supported
935 width can be retrieved in runtime by series of rte_flow_validate()
938 - 2, this engages extensive metadata mode, the ``MARK`` and ``META``
939 related actions and items operate within all supported steering domains,
940 including FDB, ``MARK`` and ``META`` information may cross the domain
941 boundaries. The ``META`` item is 32 bits wide, the ``MARK`` item width
942 depends on kernel and firmware configurations and might be 0, 16 or
943 24 bits. The actual supported width can be retrieved in runtime by
944 series of rte_flow_validate() trials.
946 - 3, this engages tunnel offload mode. In E-Switch configuration, that
947 mode implicitly activates ``dv_xmeta_en=1``.
949 +------+-----------+-----------+-------------+-------------+
950 | Mode | ``MARK`` | ``META`` | ``META`` Tx | FDB/Through |
951 +======+===========+===========+=============+=============+
952 | 0 | 24 bits | 32 bits | 32 bits | no |
953 +------+-----------+-----------+-------------+-------------+
954 | 1 | 24 bits | vary 0-32 | 32 bits | yes |
955 +------+-----------+-----------+-------------+-------------+
956 | 2 | vary 0-24 | 32 bits | 32 bits | yes |
957 +------+-----------+-----------+-------------+-------------+
959 If there is no E-Switch configuration the ``dv_xmeta_en`` parameter is
960 ignored and the device is configured to operate in legacy mode (0).
962 Disabled by default (set to 0).
964 The Direct Verbs/Rules (engaged with ``dv_flow_en`` = 1) supports all
965 of the extensive metadata features. The legacy Verbs supports FLAG and
966 MARK metadata actions over NIC Rx steering domain only.
968 Setting META value to zero in flow action means there is no item provided
969 and receiving datapath will not report in mbufs the metadata are present.
970 Setting MARK value to zero in flow action means the zero FDIR ID value
971 will be reported on packet receiving.
973 For the MARK action the last 16 values in the full range are reserved for
974 internal PMD purposes (to emulate FLAG action). The valid range for the
975 MARK action values is 0-0xFFEF for the 16-bit mode and 0-xFFFFEF
976 for the 24-bit mode, the flows with the MARK action value outside
977 the specified range will be rejected.
979 - ``dv_flow_en`` parameter [int]
981 A nonzero value enables the DV flow steering assuming it is supported
982 by the driver (RDMA Core library version is rdma-core-24.0 or higher).
984 Enabled by default if supported.
986 - ``dv_esw_en`` parameter [int]
988 A nonzero value enables E-Switch using Direct Rules.
990 Enabled by default if supported.
992 - ``lacp_by_user`` parameter [int]
994 A nonzero value enables the control of LACP traffic by the user application.
995 When a bond exists in the driver, by default it should be managed by the
996 kernel and therefore LACP traffic should be steered to the kernel.
997 If this devarg is set to 1 it will allow the user to manage the bond by
998 itself and not steer LACP traffic to the kernel.
1000 Disabled by default (set to 0).
1002 - ``mr_ext_memseg_en`` parameter [int]
1004 A nonzero value enables extending memseg when registering DMA memory. If
1005 enabled, the number of entries in MR (Memory Region) lookup table on datapath
1006 is minimized and it benefits performance. On the other hand, it worsens memory
1007 utilization because registered memory is pinned by kernel driver. Even if a
1008 page in the extended chunk is freed, that doesn't become reusable until the
1009 entire memory is freed.
1013 - ``mr_mempool_reg_en`` parameter [int]
1015 A nonzero value enables implicit registration of DMA memory of all mempools
1016 except those having ``RTE_MEMPOOL_F_NON_IO``. This flag is set automatically
1017 for mempools populated with non-contiguous objects or those without IOVA.
1018 The effect is that when a packet from a mempool is transmitted,
1019 its memory is already registered for DMA in the PMD and no registration
1020 will happen on the data path. The tradeoff is extra work on the creation
1021 of each mempool and increased HW resource use if some mempools
1022 are not used with MLX5 devices.
1026 - ``representor`` parameter [list]
1028 This parameter can be used to instantiate DPDK Ethernet devices from
1029 existing port (PF, VF or SF) representors configured on the device.
1031 It is a standard parameter whose format is described in
1032 :ref:`ethernet_device_standard_device_arguments`.
1034 For instance, to probe VF port representors 0 through 2::
1036 <PCI_BDF>,representor=vf[0-2]
1038 To probe SF port representors 0 through 2::
1040 <PCI_BDF>,representor=sf[0-2]
1042 To probe VF port representors 0 through 2 on both PFs of bonding device::
1044 <Primary_PCI_BDF>,representor=pf[0,1]vf[0-2]
1046 - ``max_dump_files_num`` parameter [int]
1048 The maximum number of files per PMD entity that may be created for debug information.
1049 The files will be created in /var/log directory or in current directory.
1051 set to 128 by default.
1053 - ``lro_timeout_usec`` parameter [int]
1055 The maximum allowed duration of an LRO session, in micro-seconds.
1056 PMD will set the nearest value supported by HW, which is not bigger than
1057 the input ``lro_timeout_usec`` value.
1058 If this parameter is not specified, by default PMD will set
1059 the smallest value supported by HW.
1061 - ``hp_buf_log_sz`` parameter [int]
1063 The total data buffer size of a hairpin queue (logarithmic form), in bytes.
1064 PMD will set the data buffer size to 2 ** ``hp_buf_log_sz``, both for RX & TX.
1065 The capacity of the value is specified by the firmware and the initialization
1066 will get a failure if it is out of scope.
1067 The range of the value is from 11 to 19 right now, and the supported frame
1068 size of a single packet for hairpin is from 512B to 128KB. It might change if
1069 different firmware release is being used. By using a small value, it could
1070 reduce memory consumption but not work with a large frame. If the value is
1071 too large, the memory consumption will be high and some potential performance
1072 degradation will be introduced.
1073 By default, the PMD will set this value to 16, which means that 9KB jumbo
1074 frames will be supported.
1076 - ``reclaim_mem_mode`` parameter [int]
1078 Cache some resources in flow destroy will help flow recreation more efficient.
1079 While some systems may require the all the resources can be reclaimed after
1081 The parameter ``reclaim_mem_mode`` provides the option for user to configure
1082 if the resource cache is needed or not.
1084 There are three options to choose:
1086 - 0. It means the flow resources will be cached as usual. The resources will
1087 be cached, helpful with flow insertion rate.
1089 - 1. It will only enable the DPDK PMD level resources reclaim.
1091 - 2. Both DPDK PMD level and rdma-core low level will be configured as
1094 By default, the PMD will set this value to 0.
1096 - ``sys_mem_en`` parameter [int]
1098 A non-zero value enables the PMD memory management allocating memory
1099 from system by default, without explicit rte memory flag.
1101 By default, the PMD will set this value to 0.
1103 - ``decap_en`` parameter [int]
1105 Some devices do not support FCS (frame checksum) scattering for
1106 tunnel-decapsulated packets.
1107 If set to 0, this option forces the FCS feature and rejects tunnel
1108 decapsulation in the flow engine for such devices.
1110 By default, the PMD will set this value to 1.
1112 - ``allow_duplicate_pattern`` parameter [int]
1114 There are two options to choose:
1116 - 0. Prevent insertion of rules with the same pattern items on non-root table.
1117 In this case, only the first rule is inserted and the following rules are
1118 rejected and error code EEXIST is returned.
1120 - 1. Allow insertion of rules with the same pattern items.
1121 In this case, all rules are inserted but only the first rule takes effect,
1122 the next rule takes effect only if the previous rules are deleted.
1124 By default, the PMD will set this value to 1.
1126 .. _mlx5_firmware_config:
1128 Firmware configuration
1129 ~~~~~~~~~~~~~~~~~~~~~~
1131 Firmware features can be configured as key/value pairs.
1133 The command to set a value is::
1135 mlxconfig -d <device> set <key>=<value>
1137 The command to query a value is::
1139 mlxconfig -d <device> query | grep <key>
1141 The device name for the command ``mlxconfig`` can be either the PCI address,
1142 or the mst device name found with::
1146 Below are some firmware configurations listed.
1152 value: 1=Infiniband 2=Ethernet 3=VPI(auto-sense)
1158 - maximum number of SR-IOV virtual functions::
1162 - enable DevX (required by Direct Rules and other features)::
1166 - aggressive CQE zipping::
1170 - L3 VXLAN and VXLAN-GPE destination UDP port::
1173 IP_OVER_VXLAN_PORT=<udp dport>
1175 - enable VXLAN-GPE tunnel flow matching::
1177 FLEX_PARSER_PROFILE_ENABLE=0
1179 FLEX_PARSER_PROFILE_ENABLE=2
1181 - enable IP-in-IP tunnel flow matching::
1183 FLEX_PARSER_PROFILE_ENABLE=0
1185 - enable MPLS flow matching::
1187 FLEX_PARSER_PROFILE_ENABLE=1
1189 - enable ICMP(code/type/identifier/sequence number) / ICMP6(code/type) fields matching::
1191 FLEX_PARSER_PROFILE_ENABLE=2
1193 - enable Geneve flow matching::
1195 FLEX_PARSER_PROFILE_ENABLE=0
1197 FLEX_PARSER_PROFILE_ENABLE=1
1199 - enable Geneve TLV option flow matching::
1201 FLEX_PARSER_PROFILE_ENABLE=0
1203 - enable GTP flow matching::
1205 FLEX_PARSER_PROFILE_ENABLE=3
1207 - enable eCPRI flow matching::
1209 FLEX_PARSER_PROFILE_ENABLE=4
1215 This driver relies on external libraries and kernel drivers for resources
1216 allocations and initialization. The following dependencies are not part of
1217 DPDK and must be installed separately:
1221 User space Verbs framework used by librte_net_mlx5. This library provides
1222 a generic interface between the kernel and low-level user space drivers
1225 It allows slow and privileged operations (context initialization, hardware
1226 resources allocations) to be managed by the kernel and fast operations to
1227 never leave user space.
1231 Low-level user space driver library for Mellanox
1232 ConnectX-4/ConnectX-5/ConnectX-6/BlueField devices, it is automatically loaded
1235 This library basically implements send/receive calls to the hardware
1238 - **Kernel modules**
1240 They provide the kernel-side Verbs API and low level device drivers that
1241 manage actual hardware initialization and resources sharing with user
1244 Unlike most other PMDs, these modules must remain loaded and bound to
1247 - mlx5_core: hardware driver managing Mellanox
1248 ConnectX-4/ConnectX-5/ConnectX-6/BlueField devices and related Ethernet kernel
1250 - mlx5_ib: InifiniBand device driver.
1251 - ib_uverbs: user space driver for Verbs (entry point for libibverbs).
1253 - **Firmware update**
1255 Mellanox OFED/EN releases include firmware updates for
1256 ConnectX-4/ConnectX-5/ConnectX-6/BlueField adapters.
1258 Because each release provides new features, these updates must be applied to
1259 match the kernel modules and libraries they come with.
1263 Both libraries are BSD and GPL licensed. Linux kernel modules are GPL
1269 Either RDMA Core library with a recent enough Linux kernel release
1270 (recommended) or Mellanox OFED/EN, which provides compatibility with older
1273 RDMA Core with Linux Kernel
1274 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
1276 - Minimal kernel version : v4.14 or the most recent 4.14-rc (see `Linux installation documentation`_)
1277 - Minimal rdma-core version: v15+ commit 0c5f5765213a ("Merge pull request #227 from yishaih/tm")
1278 (see `RDMA Core installation documentation`_)
1279 - When building for i686 use:
1281 - rdma-core version 18.0 or above built with 32bit support.
1282 - Kernel version 4.14.41 or above.
1284 - Starting with rdma-core v21, static libraries can be built::
1287 CFLAGS=-fPIC cmake -DIN_PLACE=1 -DENABLE_STATIC=1 -GNinja ..
1290 .. _`Linux installation documentation`: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/plain/Documentation/admin-guide/README.rst
1291 .. _`RDMA Core installation documentation`: https://raw.githubusercontent.com/linux-rdma/rdma-core/master/README.md
1297 - Mellanox OFED version: **4.5** and above /
1298 Mellanox EN version: **4.5** and above
1301 - ConnectX-4: **12.21.1000** and above.
1302 - ConnectX-4 Lx: **14.21.1000** and above.
1303 - ConnectX-5: **16.21.1000** and above.
1304 - ConnectX-5 Ex: **16.21.1000** and above.
1305 - ConnectX-6: **20.27.0090** and above.
1306 - ConnectX-6 Dx: **22.27.0090** and above.
1307 - BlueField: **18.25.1010** and above.
1309 While these libraries and kernel modules are available on OpenFabrics
1310 Alliance's `website <https://www.openfabrics.org/>`__ and provided by package
1311 managers on most distributions, this PMD requires Ethernet extensions that
1312 may not be supported at the moment (this is a work in progress).
1315 <http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux>`__ and
1317 <http://www.mellanox.com/page/products_dyn?product_family=27&mtag=linux>`__
1318 include the necessary support and should be used in the meantime. For DPDK,
1319 only libibverbs, libmlx5, mlnx-ofed-kernel packages and firmware updates are
1320 required from that distribution.
1324 Several versions of Mellanox OFED/EN are available. Installing the version
1325 this DPDK release was developed and tested against is strongly
1326 recommended. Please check the `linux prerequisites`_.
1328 Windows Prerequisites
1329 ---------------------
1331 This driver relies on external libraries and kernel drivers for resources
1332 allocations and initialization. The dependencies in the following sub-sections
1333 are not part of DPDK, and must be installed separately.
1335 Compilation Prerequisites
1336 ~~~~~~~~~~~~~~~~~~~~~~~~~
1338 DevX SDK installation
1339 ^^^^^^^^^^^^^^^^^^^^^
1341 The DevX SDK must be installed on the machine building the Windows PMD.
1342 Additional information can be found at
1343 `How to Integrate Windows DevX in Your Development Environment
1344 <https://docs.mellanox.com/display/winof2v250/RShim+Drivers+and+Usage#RShimDriversandUsage-DevXInterface>`__.
1346 Runtime Prerequisites
1347 ~~~~~~~~~~~~~~~~~~~~~
1349 WinOF2 version 2.60 or higher must be installed on the machine.
1354 The driver can be downloaded from the following site:
1356 <https://www.mellanox.com/products/adapter-software/ethernet/windows/winof-2>`__
1361 DevX for Windows must be enabled in the Windows registry.
1362 The keys ``DevxEnabled`` and ``DevxFsRules`` must be set.
1363 Additional information can be found in the WinOF2 user manual.
1368 The following Mellanox device families are supported by the same mlx5 driver:
1380 Below are detailed device names:
1382 * Mellanox\ |reg| ConnectX\ |reg|-4 10G MCX4111A-XCAT (1x10G)
1383 * Mellanox\ |reg| ConnectX\ |reg|-4 10G MCX412A-XCAT (2x10G)
1384 * Mellanox\ |reg| ConnectX\ |reg|-4 25G MCX4111A-ACAT (1x25G)
1385 * Mellanox\ |reg| ConnectX\ |reg|-4 25G MCX412A-ACAT (2x25G)
1386 * Mellanox\ |reg| ConnectX\ |reg|-4 40G MCX413A-BCAT (1x40G)
1387 * Mellanox\ |reg| ConnectX\ |reg|-4 40G MCX4131A-BCAT (1x40G)
1388 * Mellanox\ |reg| ConnectX\ |reg|-4 40G MCX415A-BCAT (1x40G)
1389 * Mellanox\ |reg| ConnectX\ |reg|-4 50G MCX413A-GCAT (1x50G)
1390 * Mellanox\ |reg| ConnectX\ |reg|-4 50G MCX4131A-GCAT (1x50G)
1391 * Mellanox\ |reg| ConnectX\ |reg|-4 50G MCX414A-BCAT (2x50G)
1392 * Mellanox\ |reg| ConnectX\ |reg|-4 50G MCX415A-GCAT (1x50G)
1393 * Mellanox\ |reg| ConnectX\ |reg|-4 50G MCX416A-BCAT (2x50G)
1394 * Mellanox\ |reg| ConnectX\ |reg|-4 50G MCX416A-GCAT (2x50G)
1395 * Mellanox\ |reg| ConnectX\ |reg|-4 50G MCX415A-CCAT (1x100G)
1396 * Mellanox\ |reg| ConnectX\ |reg|-4 100G MCX416A-CCAT (2x100G)
1397 * Mellanox\ |reg| ConnectX\ |reg|-4 Lx 10G MCX4111A-XCAT (1x10G)
1398 * Mellanox\ |reg| ConnectX\ |reg|-4 Lx 10G MCX4121A-XCAT (2x10G)
1399 * Mellanox\ |reg| ConnectX\ |reg|-4 Lx 25G MCX4111A-ACAT (1x25G)
1400 * Mellanox\ |reg| ConnectX\ |reg|-4 Lx 25G MCX4121A-ACAT (2x25G)
1401 * Mellanox\ |reg| ConnectX\ |reg|-4 Lx 40G MCX4131A-BCAT (1x40G)
1402 * Mellanox\ |reg| ConnectX\ |reg|-5 100G MCX556A-ECAT (2x100G)
1403 * Mellanox\ |reg| ConnectX\ |reg|-5 Ex EN 100G MCX516A-CDAT (2x100G)
1404 * Mellanox\ |reg| ConnectX\ |reg|-6 200G MCX654106A-HCAT (2x200G)
1405 * Mellanox\ |reg| ConnectX\ |reg|-6 Dx EN 100G MCX623106AN-CDAT (2x100G)
1406 * Mellanox\ |reg| ConnectX\ |reg|-6 Dx EN 200G MCX623105AN-VDAT (1x200G)
1407 * Mellanox\ |reg| ConnectX\ |reg|-6 Lx EN 25G MCX631102AN-ADAT (2x25G)
1409 Quick Start Guide on OFED/EN
1410 ----------------------------
1412 1. Download latest Mellanox OFED/EN. For more info check the `linux prerequisites`_.
1415 2. Install the required libraries and kernel modules either by installing
1416 only the required set, or by installing the entire Mellanox OFED/EN::
1418 ./mlnxofedinstall --upstream-libs --dpdk
1420 3. Verify the firmware is the correct one::
1424 4. Verify all ports links are set to Ethernet::
1426 mlxconfig -d <mst device> query | grep LINK_TYPE
1430 Link types may have to be configured to Ethernet::
1432 mlxconfig -d <mst device> set LINK_TYPE_P1/2=1/2/3
1434 * LINK_TYPE_P1=<1|2|3> , 1=Infiniband 2=Ethernet 3=VPI(auto-sense)
1436 For hypervisors, verify SR-IOV is enabled on the NIC::
1438 mlxconfig -d <mst device> query | grep SRIOV_EN
1441 If needed, configure SR-IOV::
1443 mlxconfig -d <mst device> set SRIOV_EN=1 NUM_OF_VFS=16
1444 mlxfwreset -d <mst device> reset
1446 5. Restart the driver::
1448 /etc/init.d/openibd restart
1452 service openibd restart
1454 If link type was changed, firmware must be reset as well::
1456 mlxfwreset -d <mst device> reset
1458 For hypervisors, after reset write the sysfs number of virtual functions
1461 To dynamically instantiate a given number of virtual functions (VFs)::
1463 echo [num_vfs] > /sys/class/infiniband/mlx5_0/device/sriov_numvfs
1465 6. Install DPDK and you are ready to go.
1466 See :doc:`compilation instructions <../linux_gsg/build_dpdk>`.
1468 Enable switchdev mode
1469 ---------------------
1471 Switchdev mode is a mode in E-Switch, that binds between representor and VF or SF.
1472 Representor is a port in DPDK that is connected to a VF or SF in such a way
1473 that assuming there are no offload flows, each packet that is sent from the VF or SF
1474 will be received by the corresponding representor. While each packet that is or SF
1475 sent to a representor will be received by the VF or SF.
1476 This is very useful in case of SRIOV mode, where the first packet that is sent
1477 by the VF or SF will be received by the DPDK application which will decide if this
1478 flow should be offloaded to the E-Switch. After offloading the flow packet
1479 that the VF or SF that are matching the flow will not be received any more by
1480 the DPDK application.
1482 1. Enable SRIOV mode::
1484 mlxconfig -d <mst device> set SRIOV_EN=true
1486 2. Configure the max number of VFs::
1488 mlxconfig -d <mst device> set NUM_OF_VFS=<num of vfs>
1492 mlxfwreset -d <mst device> reset
1494 3. Configure the actual number of VFs::
1496 echo <num of vfs > /sys/class/net/<net device>/device/sriov_numvfs
1498 4. Unbind the device (can be rebind after the switchdev mode)::
1500 echo -n "<device pci address" > /sys/bus/pci/drivers/mlx5_core/unbind
1502 5. Enable switchdev mode::
1504 echo switchdev > /sys/class/net/<net device>/compat/devlink/mode
1506 Sub-Function support
1507 --------------------
1509 Sub-Function is a portion of the PCI device, a SF netdev has its own
1510 dedicated queues (txq, rxq).
1511 A SF shares PCI level resources with other SFs and/or with its parent PCI function.
1515 OFED version >= 5.4-0.3.3.0
1517 1. Configure SF feature::
1519 # Run mlxconfig on both PFs on host and ECPFs on BlueField.
1520 mlxconfig -d <mst device> set PER_PF_NUM_SF=1 PF_TOTAL_SF=252 PF_SF_BAR_SIZE=12
1522 2. Enable switchdev mode::
1524 mlxdevm dev eswitch set pci/<DBDF> mode switchdev
1528 mlxdevm port add pci/<DBDF> flavour pcisf pfnum 0 sfnum <sfnum>
1530 Get SFID from output: pci/<DBDF>/<SFID>
1532 4. Modify MAC address::
1534 mlxdevm port function set pci/<DBDF>/<SFID> hw_addr <MAC>
1536 5. Activate SF port::
1538 mlxdevm port function set pci/<DBDF>/<ID> state active
1540 6. Devargs to probe SF device::
1542 auxiliary:mlx5_core.sf.<num>,dv_flow_en=1
1544 Sub-Function representor support
1545 --------------------------------
1547 A SF netdev supports E-Switch representation offload
1548 similar to PF and VF representors.
1549 Use <sfnum> to probe SF representor::
1551 testpmd> port attach <PCI_BDF>,representor=sf<sfnum>,dv_flow_en=1
1556 1. Configure aggressive CQE Zipping for maximum performance::
1558 mlxconfig -d <mst device> s CQE_COMPRESSION=1
1560 To set it back to the default CQE Zipping mode use::
1562 mlxconfig -d <mst device> s CQE_COMPRESSION=0
1564 2. In case of virtualization:
1566 - Make sure that hypervisor kernel is 3.16 or newer.
1567 - Configure boot with ``iommu=pt``.
1568 - Use 1G huge pages.
1569 - Make sure to allocate a VM on huge pages.
1570 - Make sure to set CPU pinning.
1572 3. Use the CPU near local NUMA node to which the PCIe adapter is connected,
1573 for better performance. For VMs, verify that the right CPU
1574 and NUMA node are pinned according to the above. Run::
1576 lstopo-no-graphics --merge
1578 to identify the NUMA node to which the PCIe adapter is connected.
1580 4. If more than one adapter is used, and root complex capabilities allow
1581 to put both adapters on the same NUMA node without PCI bandwidth degradation,
1582 it is recommended to locate both adapters on the same NUMA node.
1583 This in order to forward packets from one to the other without
1584 NUMA performance penalty.
1586 5. Disable pause frames::
1588 ethtool -A <netdev> rx off tx off
1590 6. Verify IO non-posted prefetch is disabled by default. This can be checked
1591 via the BIOS configuration. Please contact you server provider for more
1592 information about the settings.
1596 On some machines, depends on the machine integrator, it is beneficial
1597 to set the PCI max read request parameter to 1K. This can be
1598 done in the following way:
1600 To query the read request size use::
1602 setpci -s <NIC PCI address> 68.w
1604 If the output is different than 3XXX, set it by::
1606 setpci -s <NIC PCI address> 68.w=3XXX
1608 The XXX can be different on different systems. Make sure to configure
1609 according to the setpci output.
1611 7. To minimize overhead of searching Memory Regions:
1613 - '--socket-mem' is recommended to pin memory by predictable amount.
1614 - Configure per-lcore cache when creating Mempools for packet buffer.
1615 - Refrain from dynamically allocating/freeing memory in run-time.
1620 There are multiple Rx burst functions with different advantages and limitations.
1622 .. table:: Rx burst functions
1624 +-------------------+------------------------+---------+-----------------+------+-------+
1625 || Function Name || Enabler || Scatter|| Error Recovery || CQE || Large|
1626 | | | | || comp|| MTU |
1627 +===================+========================+=========+=================+======+=======+
1628 | rx_burst | rx_vec_en=0 | Yes | Yes | Yes | Yes |
1629 +-------------------+------------------------+---------+-----------------+------+-------+
1630 | rx_burst_vec | rx_vec_en=1 (default) | No | if CQE comp off | Yes | No |
1631 +-------------------+------------------------+---------+-----------------+------+-------+
1632 | rx_burst_mprq || mprq_en=1 | No | Yes | Yes | Yes |
1633 | || RxQs >= rxqs_min_mprq | | | | |
1634 +-------------------+------------------------+---------+-----------------+------+-------+
1635 | rx_burst_mprq_vec || rx_vec_en=1 (default) | No | if CQE comp off | Yes | Yes |
1636 | || mprq_en=1 | | | | |
1637 | || RxQs >= rxqs_min_mprq | | | | |
1638 +-------------------+------------------------+---------+-----------------+------+-------+
1640 .. _mlx5_offloads_support:
1642 Supported hardware offloads
1643 ---------------------------
1645 .. table:: Minimal SW/HW versions for queue offloads
1647 ============== ===== ===== ========= ===== ========== =============
1648 Offload DPDK Linux rdma-core OFED firmware hardware
1649 ============== ===== ===== ========= ===== ========== =============
1650 common base 17.11 4.14 16 4.2-1 12.21.1000 ConnectX-4
1651 checksums 17.11 4.14 16 4.2-1 12.21.1000 ConnectX-4
1652 Rx timestamp 17.11 4.14 16 4.2-1 12.21.1000 ConnectX-4
1653 TSO 17.11 4.14 16 4.2-1 12.21.1000 ConnectX-4
1654 LRO 19.08 N/A N/A 4.6-4 16.25.6406 ConnectX-5
1655 Tx scheduling 20.08 N/A N/A 5.1-2 22.28.2006 ConnectX-6 Dx
1656 Buffer Split 20.11 N/A N/A 5.1-2 16.28.2006 ConnectX-5
1657 ============== ===== ===== ========= ===== ========== =============
1659 .. table:: Minimal SW/HW versions for rte_flow offloads
1661 +-----------------------+-----------------+-----------------+
1662 | Offload | with E-Switch | with NIC |
1663 +=======================+=================+=================+
1664 | Count | | DPDK 19.05 | | DPDK 19.02 |
1665 | | | OFED 4.6 | | OFED 4.6 |
1666 | | | rdma-core 24 | | rdma-core 23 |
1667 | | | ConnectX-5 | | ConnectX-5 |
1668 +-----------------------+-----------------+-----------------+
1669 | Drop | | DPDK 19.05 | | DPDK 18.11 |
1670 | | | OFED 4.6 | | OFED 4.5 |
1671 | | | rdma-core 24 | | rdma-core 23 |
1672 | | | ConnectX-5 | | ConnectX-4 |
1673 +-----------------------+-----------------+-----------------+
1674 | Queue / RSS | | | | DPDK 18.11 |
1675 | | | N/A | | OFED 4.5 |
1676 | | | | | rdma-core 23 |
1677 | | | | | ConnectX-4 |
1678 +-----------------------+-----------------+-----------------+
1679 | Shared action | | | | |
1680 | | | :numref:`sact`| | :numref:`sact`|
1683 +-----------------------+-----------------+-----------------+
1684 | | VLAN | | DPDK 19.11 | | DPDK 19.11 |
1685 | | (of_pop_vlan / | | OFED 4.7-1 | | OFED 4.7-1 |
1686 | | of_push_vlan / | | ConnectX-5 | | ConnectX-5 |
1687 | | of_set_vlan_pcp / | | | | |
1688 | | of_set_vlan_vid) | | | | |
1689 +-----------------------+-----------------+-----------------+
1690 | | VLAN | | DPDK 21.05 | | |
1691 | | ingress and / | | OFED 5.3 | | N/A |
1692 | | of_push_vlan / | | ConnectX-6 Dx | | |
1693 +-----------------------+-----------------+-----------------+
1694 | | VLAN | | DPDK 21.05 | | |
1695 | | egress and / | | OFED 5.3 | | N/A |
1696 | | of_pop_vlan / | | ConnectX-6 Dx | | |
1697 +-----------------------+-----------------+-----------------+
1698 | Encapsulation | | DPDK 19.05 | | DPDK 19.02 |
1699 | (VXLAN / NVGRE / RAW) | | OFED 4.7-1 | | OFED 4.6 |
1700 | | | rdma-core 24 | | rdma-core 23 |
1701 | | | ConnectX-5 | | ConnectX-5 |
1702 +-----------------------+-----------------+-----------------+
1703 | Encapsulation | | DPDK 19.11 | | DPDK 19.11 |
1704 | GENEVE | | OFED 4.7-3 | | OFED 4.7-3 |
1705 | | | rdma-core 27 | | rdma-core 27 |
1706 | | | ConnectX-5 | | ConnectX-5 |
1707 +-----------------------+-----------------+-----------------+
1708 | Tunnel Offload | | DPDK 20.11 | | DPDK 20.11 |
1709 | | | OFED 5.1-2 | | OFED 5.1-2 |
1710 | | | rdma-core 32 | | N/A |
1711 | | | ConnectX-5 | | ConnectX-5 |
1712 +-----------------------+-----------------+-----------------+
1713 | | Header rewrite | | DPDK 19.05 | | DPDK 19.02 |
1714 | | (set_ipv4_src / | | OFED 4.7-1 | | OFED 4.7-1 |
1715 | | set_ipv4_dst / | | rdma-core 24 | | rdma-core 24 |
1716 | | set_ipv6_src / | | ConnectX-5 | | ConnectX-5 |
1717 | | set_ipv6_dst / | | | | |
1718 | | set_tp_src / | | | | |
1719 | | set_tp_dst / | | | | |
1720 | | dec_ttl / | | | | |
1721 | | set_ttl / | | | | |
1722 | | set_mac_src / | | | | |
1723 | | set_mac_dst) | | | | |
1724 +-----------------------+-----------------+-----------------+
1725 | | Header rewrite | | DPDK 20.02 | | DPDK 20.02 |
1726 | | (set_dscp) | | OFED 5.0 | | OFED 5.0 |
1727 | | | | rdma-core 24 | | rdma-core 24 |
1728 | | | | ConnectX-5 | | ConnectX-5 |
1729 +-----------------------+-----------------+-----------------+
1730 | Jump | | DPDK 19.05 | | DPDK 19.02 |
1731 | | | OFED 4.7-1 | | OFED 4.7-1 |
1732 | | | rdma-core 24 | | N/A |
1733 | | | ConnectX-5 | | ConnectX-5 |
1734 +-----------------------+-----------------+-----------------+
1735 | Mark / Flag | | DPDK 19.05 | | DPDK 18.11 |
1736 | | | OFED 4.6 | | OFED 4.5 |
1737 | | | rdma-core 24 | | rdma-core 23 |
1738 | | | ConnectX-5 | | ConnectX-4 |
1739 +-----------------------+-----------------+-----------------+
1740 | Meta data | | DPDK 19.11 | | DPDK 19.11 |
1741 | | | OFED 4.7-3 | | OFED 4.7-3 |
1742 | | | rdma-core 26 | | rdma-core 26 |
1743 | | | ConnectX-5 | | ConnectX-5 |
1744 +-----------------------+-----------------+-----------------+
1745 | Port ID | | DPDK 19.05 | | N/A |
1746 | | | OFED 4.7-1 | | N/A |
1747 | | | rdma-core 24 | | N/A |
1748 | | | ConnectX-5 | | N/A |
1749 +-----------------------+-----------------+-----------------+
1750 | Hairpin | | | | DPDK 19.11 |
1751 | | | N/A | | OFED 4.7-3 |
1752 | | | | | rdma-core 26 |
1753 | | | | | ConnectX-5 |
1754 +-----------------------+-----------------+-----------------+
1755 | 2-port Hairpin | | | | DPDK 20.11 |
1756 | | | N/A | | OFED 5.1-2 |
1758 | | | | | ConnectX-5 |
1759 +-----------------------+-----------------+-----------------+
1760 | Metering | | DPDK 19.11 | | DPDK 19.11 |
1761 | | | OFED 4.7-3 | | OFED 4.7-3 |
1762 | | | rdma-core 26 | | rdma-core 26 |
1763 | | | ConnectX-5 | | ConnectX-5 |
1764 +-----------------------+-----------------+-----------------+
1765 | ASO Metering | | DPDK 21.05 | | DPDK 21.05 |
1766 | | | OFED 5.3 | | OFED 5.3 |
1767 | | | rdma-core 33 | | rdma-core 33 |
1768 | | | ConnectX-6 Dx| | ConnectX-6 Dx |
1769 +-----------------------+-----------------+-----------------+
1770 | Metering Hierarchy | | DPDK 21.08 | | DPDK 21.08 |
1771 | | | OFED 5.3 | | OFED 5.3 |
1773 | | | ConnectX-6 Dx| | ConnectX-6 Dx |
1774 +-----------------------+-----------------+-----------------+
1775 | Sampling | | DPDK 20.11 | | DPDK 20.11 |
1776 | | | OFED 5.1-2 | | OFED 5.1-2 |
1777 | | | rdma-core 32 | | N/A |
1778 | | | ConnectX-5 | | ConnectX-5 |
1779 +-----------------------+-----------------+-----------------+
1780 | Encapsulation | | DPDK 21.02 | | DPDK 21.02 |
1781 | GTP PSC | | OFED 5.2 | | OFED 5.2 |
1782 | | | rdma-core 35 | | rdma-core 35 |
1783 | | | ConnectX-6 Dx| | ConnectX-6 Dx |
1784 +-----------------------+-----------------+-----------------+
1785 | Encapsulation | | DPDK 21.02 | | DPDK 21.02 |
1786 | GENEVE TLV option | | OFED 5.2 | | OFED 5.2 |
1787 | | | rdma-core 34 | | rdma-core 34 |
1788 | | | ConnectX-6 Dx | | ConnectX-6 Dx |
1789 +-----------------------+-----------------+-----------------+
1790 | Modify Field | | DPDK 21.02 | | DPDK 21.02 |
1791 | | | OFED 5.2 | | OFED 5.2 |
1792 | | | rdma-core 35 | | rdma-core 35 |
1793 | | | ConnectX-5 | | ConnectX-5 |
1794 +-----------------------+-----------------+-----------------+
1795 | Connection tracking | | | | DPDK 21.05 |
1796 | | | N/A | | OFED 5.3 |
1797 | | | | | rdma-core 35 |
1798 | | | | | ConnectX-6 Dx |
1799 +-----------------------+-----------------+-----------------+
1801 .. table:: Minimal SW/HW versions for shared action offload
1804 +-----------------------+-----------------+-----------------+
1805 | Shared Action | with E-Switch | with NIC |
1806 +=======================+=================+=================+
1807 | RSS | | | | DPDK 20.11 |
1808 | | | N/A | | OFED 5.2 |
1809 | | | | | rdma-core 33 |
1810 | | | | | ConnectX-5 |
1811 +-----------------------+-----------------+-----------------+
1812 | Age | | DPDK 20.11 | | DPDK 20.11 |
1813 | | | OFED 5.2 | | OFED 5.2 |
1814 | | | rdma-core 32 | | rdma-core 32 |
1815 | | | ConnectX-6 Dx | | ConnectX-6 Dx |
1816 +-----------------------+-----------------+-----------------+
1817 | Count | | DPDK 21.05 | | DPDK 21.05 |
1818 | | | OFED 4.6 | | OFED 4.6 |
1819 | | | rdma-core 24 | | rdma-core 23 |
1820 | | | ConnectX-5 | | ConnectX-5 |
1821 +-----------------------+-----------------+-----------------+
1826 MARK and META items are interrelated with datapath - they might move from/to
1827 the applications in mbuf fields. Hence, zero value for these items has the
1828 special meaning - it means "no metadata are provided", not zero values are
1829 treated by applications and PMD as valid ones.
1831 Moreover in the flow engine domain the value zero is acceptable to match and
1832 set, and we should allow to specify zero values as rte_flow parameters for the
1833 META and MARK items and actions. In the same time zero mask has no meaning and
1834 should be rejected on validation stage.
1839 Flows are not cached in the driver.
1840 When stopping a device port, all the flows created on this port from the
1841 application will be flushed automatically in the background.
1842 After stopping the device port, all flows on this port become invalid and
1843 not represented in the system.
1844 All references to these flows held by the application should be discarded
1845 directly but neither destroyed nor flushed.
1847 The application should re-create the flows as required after the port restart.
1852 Compared to librte_net_mlx4 that implements a single RSS configuration per
1853 port, librte_net_mlx5 supports per-protocol RSS configuration.
1855 Since ``testpmd`` defaults to IP RSS mode and there is currently no
1856 command-line parameter to enable additional protocols (UDP and TCP as well
1857 as IP), the following commands must be entered from its CLI to get the same
1858 behavior as librte_net_mlx4::
1861 > port config all rss all
1867 This section demonstrates how to launch **testpmd** with Mellanox
1868 ConnectX-4/ConnectX-5/ConnectX-6/BlueField devices managed by librte_net_mlx5.
1870 #. Load the kernel modules::
1872 modprobe -a ib_uverbs mlx5_core mlx5_ib
1874 Alternatively if MLNX_OFED/MLNX_EN is fully installed, the following script
1877 /etc/init.d/openibd restart
1881 User space I/O kernel modules (uio and igb_uio) are not used and do
1882 not have to be loaded.
1884 #. Make sure Ethernet interfaces are in working order and linked to kernel
1885 verbs. Related sysfs entries should be present::
1887 ls -d /sys/class/net/*/device/infiniband_verbs/uverbs* | cut -d / -f 5
1896 #. Optionally, retrieve their PCI bus addresses for to be used with the allow list::
1899 for intf in eth2 eth3 eth4 eth5;
1901 (cd "/sys/class/net/${intf}/device/" && pwd -P);
1904 sed -n 's,.*/\(.*\),-a \1,p'
1913 #. Request huge pages::
1915 dpdk-hugepages.py --setup 2G
1917 #. Start testpmd with basic parameters::
1919 dpdk-testpmd -l 8-15 -n 4 -a 05:00.0 -a 05:00.1 -a 06:00.0 -a 06:00.1 -- --rxq=2 --txq=2 -i
1924 EAL: PCI device 0000:05:00.0 on NUMA socket 0
1925 EAL: probe driver: 15b3:1013 librte_net_mlx5
1926 PMD: librte_net_mlx5: PCI information matches, using device "mlx5_0" (VF: false)
1927 PMD: librte_net_mlx5: 1 port(s) detected
1928 PMD: librte_net_mlx5: port 1 MAC address is e4:1d:2d:e7:0c:fe
1929 EAL: PCI device 0000:05:00.1 on NUMA socket 0
1930 EAL: probe driver: 15b3:1013 librte_net_mlx5
1931 PMD: librte_net_mlx5: PCI information matches, using device "mlx5_1" (VF: false)
1932 PMD: librte_net_mlx5: 1 port(s) detected
1933 PMD: librte_net_mlx5: port 1 MAC address is e4:1d:2d:e7:0c:ff
1934 EAL: PCI device 0000:06:00.0 on NUMA socket 0
1935 EAL: probe driver: 15b3:1013 librte_net_mlx5
1936 PMD: librte_net_mlx5: PCI information matches, using device "mlx5_2" (VF: false)
1937 PMD: librte_net_mlx5: 1 port(s) detected
1938 PMD: librte_net_mlx5: port 1 MAC address is e4:1d:2d:e7:0c:fa
1939 EAL: PCI device 0000:06:00.1 on NUMA socket 0
1940 EAL: probe driver: 15b3:1013 librte_net_mlx5
1941 PMD: librte_net_mlx5: PCI information matches, using device "mlx5_3" (VF: false)
1942 PMD: librte_net_mlx5: 1 port(s) detected
1943 PMD: librte_net_mlx5: port 1 MAC address is e4:1d:2d:e7:0c:fb
1944 Interactive-mode selected
1945 Configuring Port 0 (socket 0)
1946 PMD: librte_net_mlx5: 0x8cba80: TX queues number update: 0 -> 2
1947 PMD: librte_net_mlx5: 0x8cba80: RX queues number update: 0 -> 2
1948 Port 0: E4:1D:2D:E7:0C:FE
1949 Configuring Port 1 (socket 0)
1950 PMD: librte_net_mlx5: 0x8ccac8: TX queues number update: 0 -> 2
1951 PMD: librte_net_mlx5: 0x8ccac8: RX queues number update: 0 -> 2
1952 Port 1: E4:1D:2D:E7:0C:FF
1953 Configuring Port 2 (socket 0)
1954 PMD: librte_net_mlx5: 0x8cdb10: TX queues number update: 0 -> 2
1955 PMD: librte_net_mlx5: 0x8cdb10: RX queues number update: 0 -> 2
1956 Port 2: E4:1D:2D:E7:0C:FA
1957 Configuring Port 3 (socket 0)
1958 PMD: librte_net_mlx5: 0x8ceb58: TX queues number update: 0 -> 2
1959 PMD: librte_net_mlx5: 0x8ceb58: RX queues number update: 0 -> 2
1960 Port 3: E4:1D:2D:E7:0C:FB
1961 Checking link statuses...
1962 Port 0 Link Up - speed 40000 Mbps - full-duplex
1963 Port 1 Link Up - speed 40000 Mbps - full-duplex
1964 Port 2 Link Up - speed 10000 Mbps - full-duplex
1965 Port 3 Link Up - speed 10000 Mbps - full-duplex
1972 This section demonstrates how to dump flows. Currently, it's possible to dump
1973 all flows with assistance of external tools.
1975 #. 2 ways to get flow raw file:
1977 - Using testpmd CLI:
1979 .. code-block:: console
1982 testpmd> flow dump <port> all <output_file>
1984 testpmd> flow dump <port> rule <rule_id> <output_file>
1986 - call rte_flow_dev_dump api:
1988 .. code-block:: console
1990 rte_flow_dev_dump(port, flow, file, NULL);
1992 #. Dump human-readable flows from raw file:
1994 Get flow parsing tool from: https://github.com/Mellanox/mlx_steering_dump
1996 .. code-block:: console
1998 mlx_steering_dump.py -f <output_file> -flowptr <flow_ptr>
2000 How to share a meter between ports in the same switch domain
2001 ------------------------------------------------------------
2003 This section demonstrates how to use the shared meter. A meter M can be created
2004 on port X and to be shared with a port Y on the same switch domain by the next way:
2006 .. code-block:: console
2008 flow create X ingress transfer pattern eth / port_id id is Y / end actions meter mtr_id M / end
2010 How to use meter hierarchy
2011 --------------------------
2013 This section demonstrates how to create and use a meter hierarchy.
2014 A termination meter M can be the policy green action of another termination meter N.
2015 The two meters are chained together as a chain. Using meter N in a flow will apply
2016 both the meters in hierarchy on that flow.
2018 .. code-block:: console
2020 add port meter policy 0 1 g_actions queue index 0 / end y_actions end r_actions drop / end
2021 create port meter 0 M 1 1 yes 0xffff 1 0
2022 add port meter policy 0 2 g_actions meter mtr_id M / end y_actions end r_actions drop / end
2023 create port meter 0 N 2 2 yes 0xffff 1 0
2024 flow create 0 ingress group 1 pattern eth / end actions meter mtr_id N / end