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 GTP extension header with raw encap/decap action.
103 - Matching on Geneve TLV option header with raw encap/decap action.
104 - RSS support in sample action.
105 - E-Switch mirroring and jump.
106 - E-Switch mirroring and modify.
107 - 21844 flow priorities for ingress or egress flow groups greater than 0 and for any transfer
109 - Flow metering, including meter policy API.
110 - Flow meter hierarchy.
111 - Flow integrity offload API.
112 - Connection tracking.
113 - Sub-Function representors.
120 On Windows, the features are limited:
122 - Promiscuous mode is not supported
123 - The following rules are supported:
125 - IPv4/UDP with CVLAN filtering
126 - Unicast MAC filtering
128 - Additional rules are supported from WinOF2 version 2.70:
130 - IPv4/TCP with CVLAN filtering
131 - L4 steering rules for port RSS of UDP, TCP and IP
133 - For secondary process:
135 - Forked secondary process not supported.
136 - External memory unregistered in EAL memseg list cannot be used for DMA
137 unless such memory has been registered by ``mlx5_mr_update_ext_mp()`` in
138 primary process and remapped to the same virtual address in secondary
139 process. If the external memory is registered by primary process but has
140 different virtual address in secondary process, unexpected error may happen.
142 - When using Verbs flow engine (``dv_flow_en`` = 0), flow pattern without any
143 specific VLAN will match for VLAN packets as well:
145 When VLAN spec is not specified in the pattern, the matching rule will be created with VLAN as a wild card.
146 Meaning, the flow rule::
148 flow create 0 ingress pattern eth / vlan vid is 3 / ipv4 / end ...
150 Will only match vlan packets with vid=3. and the flow rule::
152 flow create 0 ingress pattern eth / ipv4 / end ...
154 Will match any ipv4 packet (VLAN included).
156 - When using Verbs flow engine (``dv_flow_en`` = 0), multi-tagged(QinQ) match is not supported.
158 - 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.
161 flow create 0 ingress pattern eth / ipv4 / end ...
163 Will match any ipv4 packet.
166 flow create 0 ingress pattern eth / vlan / end ...
167 flow create 0 ingress pattern eth has_vlan is 1 / end ...
168 flow create 0 ingress pattern eth type is 0x8100 / end ...
170 Will match single-tagged packets only, with any VLAN ID value.
173 flow create 0 ingress pattern eth type is 0x88A8 / end ...
174 flow create 0 ingress pattern eth / vlan has_more_vlan is 1 / end ...
176 Will match multi-tagged packets only, with any VLAN ID value.
178 - A flow pattern with 2 sequential VLAN items is not supported.
180 - VLAN pop offload command:
182 - Flow rules having a VLAN pop offload command as one of their actions and
183 are lacking a match on VLAN as one of their items are not supported.
184 - The command is not supported on egress traffic in NIC mode.
186 - VLAN push offload is not supported on ingress traffic in NIC mode.
188 - VLAN set PCP offload is not supported on existing headers.
190 - A multi segment packet must have not more segments than reported by dev_infos_get()
191 in tx_desc_lim.nb_seg_max field. This value depends on maximal supported Tx descriptor
192 size and ``txq_inline_min`` settings and may be from 2 (worst case forced by maximal
193 inline settings) to 58.
195 - Match on VXLAN supports the following fields only:
198 - Last reserved 8-bits
200 Last reserved 8-bits matching is only supported When using DV flow
201 engine (``dv_flow_en`` = 1).
202 Group zero's behavior may differ which depends on FW.
203 Matching value equals 0 (value & mask) is not supported.
205 - L3 VXLAN and VXLAN-GPE tunnels cannot be supported together with MPLSoGRE and MPLSoUDP.
207 - Match on Geneve header supports the following fields only:
214 - Match on Geneve TLV option is supported on the following fields:
221 Only one Class/Type/Length Geneve TLV option is supported per shared device.
222 Class/Type/Length fields must be specified as well as masks.
223 Class/Type/Length specified masks must be full.
224 Matching Geneve TLV option without specifying data is not supported.
225 Matching Geneve TLV option with ``data & mask == 0`` is not supported.
227 - VF: flow rules created on VF devices can only match traffic targeted at the
228 configured MAC addresses (see ``rte_eth_dev_mac_addr_add()``).
230 - Match on GTP tunnel header item supports the following fields only:
232 - v_pt_rsv_flags: E flag, S flag, PN flag
236 - Match on GTP extension header only for GTP PDU session container (next
237 extension header type = 0x85).
238 - Match on GTP extension header is not supported in group 0.
240 - No Tx metadata go to the E-Switch steering domain for the Flow group 0.
241 The flows within group 0 and set metadata action are rejected by hardware.
245 MAC addresses not already present in the bridge table of the associated
246 kernel network device will be added and cleaned up by the PMD when closing
247 the device. In case of ungraceful program termination, some entries may
248 remain present and should be removed manually by other means.
250 - Buffer split offload is supported with regular Rx burst routine only,
251 no MPRQ feature or vectorized code can be engaged.
253 - When Multi-Packet Rx queue is configured (``mprq_en``), a Rx packet can be
254 externally attached to a user-provided mbuf with having EXT_ATTACHED_MBUF in
255 ol_flags. As the mempool for the external buffer is managed by PMD, all the
256 Rx mbufs must be freed before the device is closed. Otherwise, the mempool of
257 the external buffers will be freed by PMD and the application which still
258 holds the external buffers may be corrupted.
260 - If Multi-Packet Rx queue is configured (``mprq_en``) and Rx CQE compression is
261 enabled (``rxq_cqe_comp_en``) at the same time, RSS hash result is not fully
262 supported. Some Rx packets may not have PKT_RX_RSS_HASH.
264 - IPv6 Multicast messages are not supported on VM, while promiscuous mode
265 and allmulticast mode are both set to off.
266 To receive IPv6 Multicast messages on VM, explicitly set the relevant
267 MAC address using rte_eth_dev_mac_addr_add() API.
269 - To support a mixed traffic pattern (some buffers from local host memory, some
270 buffers from other devices) with high bandwidth, a mbuf flag is used.
272 An application hints the PMD whether or not it should try to inline the
273 given mbuf data buffer. PMD should do the best effort to act upon this request.
275 The hint flag ``RTE_PMD_MLX5_FINE_GRANULARITY_INLINE`` is dynamic,
276 registered by application with rte_mbuf_dynflag_register(). This flag is
277 purely driver-specific and declared in PMD specific header ``rte_pmd_mlx5.h``,
278 which is intended to be used by the application.
280 To query the supported specific flags in runtime,
281 the function ``rte_pmd_mlx5_get_dyn_flag_names`` returns the array of
282 currently (over present hardware and configuration) supported specific flags.
283 The "not inline hint" feature operating flow is the following one:
286 - probe the devices, ports are created
287 - query the port capabilities
288 - if port supporting the feature is found
289 - register dynamic flag ``RTE_PMD_MLX5_FINE_GRANULARITY_INLINE``
290 - application starts the ports
291 - on ``dev_start()`` PMD checks whether the feature flag is registered and
292 enables the feature support in datapath
293 - application might set the registered flag bit in ``ol_flags`` field
294 of mbuf being sent and PMD will handle ones appropriately.
296 - The amount of descriptors in Tx queue may be limited by data inline settings.
297 Inline data require the more descriptor building blocks and overall block
298 amount may exceed the hardware supported limits. The application should
299 reduce the requested Tx size or adjust data inline settings with
300 ``txq_inline_max`` and ``txq_inline_mpw`` devargs keys.
302 - To provide the packet send scheduling on mbuf timestamps the ``tx_pp``
303 parameter should be specified.
304 When PMD sees the RTE_MBUF_DYNFLAG_TX_TIMESTAMP_NAME set on the packet
305 being sent it tries to synchronize the time of packet appearing on
306 the wire with the specified packet timestamp. It the specified one
307 is in the past it should be ignored, if one is in the distant future
308 it should be capped with some reasonable value (in range of seconds).
309 These specific cases ("too late" and "distant future") can be optionally
310 reported via device xstats to assist applications to detect the
311 time-related problems.
313 The timestamp upper "too-distant-future" limit
314 at the moment of invoking the Tx burst routine
315 can be estimated as ``tx_pp`` option (in nanoseconds) multiplied by 2^23.
316 Please note, for the testpmd txonly mode,
317 the limit is deduced from the expression::
319 (n_tx_descriptors / burst_size + 1) * inter_burst_gap
321 There is no any packet reordering according timestamps is supposed,
322 neither within packet burst, nor between packets, it is an entirely
323 application responsibility to generate packets and its timestamps
324 in desired order. The timestamps can be put only in the first packet
325 in the burst providing the entire burst scheduling.
327 - E-Switch decapsulation Flow:
329 - can be applied to PF port only.
330 - must specify VF port action (packet redirection from PF to VF).
331 - optionally may specify tunnel inner source and destination MAC addresses.
333 - E-Switch encapsulation Flow:
335 - can be applied to VF ports only.
336 - must specify PF port action (packet redirection from VF to PF).
340 - The input buffer, used as outer header, is not validated.
344 - The decapsulation is always done up to the outermost tunnel detected by the HW.
345 - The input buffer, providing the removal size, is not validated.
346 - The buffer size must match the length of the headers to be removed.
348 - ICMP(code/type/identifier/sequence number) / ICMP6(code/type) matching, IP-in-IP and MPLS flow matching are all
349 mutually exclusive features which cannot be supported together
350 (see :ref:`mlx5_firmware_config`).
354 - Requires DevX and DV flow to be enabled.
355 - KEEP_CRC offload cannot be supported with LRO.
356 - The first mbuf length, without head-room, must be big enough to include the
358 - Rx queue with LRO offload enabled, receiving a non-LRO packet, can forward
359 it with size limited to max LRO size, not to max RX packet length.
360 - LRO can be used with outer header of TCP packets of the standard format:
361 eth (with or without vlan) / ipv4 or ipv6 / tcp / payload
363 Other TCP packets (e.g. with MPLS label) received on Rx queue with LRO enabled, will be received with bad checksum.
364 - LRO packet aggregation is performed by HW only for packet size larger than
365 ``lro_min_mss_size``. This value is reported on device start, when debug
370 - ``DEV_RX_OFFLOAD_KEEP_CRC`` cannot be supported with decapsulation
371 for some NICs (such as ConnectX-6 Dx, ConnectX-6 Lx, and BlueField-2).
372 The capability bit ``scatter_fcs_w_decap_disable`` shows NIC support.
376 - fast free offload assumes the all mbufs being sent are originated from the
377 same memory pool and there is no any extra references to the mbufs (the
378 reference counter for each mbuf is equal 1 on tx_burst call). The latter
379 means there should be no any externally attached buffers in mbufs. It is
380 an application responsibility to provide the correct mbufs if the fast
381 free offload is engaged. The mlx5 PMD implicitly produces the mbufs with
382 externally attached buffers if MPRQ option is enabled, hence, the fast
383 free offload is neither supported nor advertised if there is MPRQ enabled.
387 - Supports ``RTE_FLOW_ACTION_TYPE_SAMPLE`` action only within NIC Rx and
388 E-Switch steering domain.
389 - For E-Switch Sampling flow with sample ratio > 1, additional actions are not
390 supported in the sample actions list.
391 - For ConnectX-5, the ``RTE_FLOW_ACTION_TYPE_SAMPLE`` is typically used as
392 first action in the E-Switch egress flow if with header modify or
393 encapsulation actions.
394 - For NIC Rx flow, supports ``MARK``, ``COUNT``, ``QUEUE``, ``RSS`` in the
396 - For E-Switch mirroring flow, supports ``RAW ENCAP``, ``Port ID``,
397 ``VXLAN ENCAP``, ``NVGRE ENCAP`` in the sample actions list.
401 - Supports the 'set' operation only for ``RTE_FLOW_ACTION_TYPE_MODIFY_FIELD`` action.
402 - Modification of an arbitrary place in a packet via the special ``RTE_FLOW_FIELD_START`` Field ID is not supported.
403 - Modification of the 802.1Q Tag, VXLAN Network or GENEVE Network ID's is not supported.
404 - Encapsulation levels are not supported, can modify outermost header fields only.
405 - Offsets must be 32-bits aligned, cannot skip past the boundary of a field.
407 - IPv6 header item 'proto' field, indicating the next header protocol, should
408 not be set as extension header.
409 In case the next header is an extension header, it should not be specified in
410 IPv6 header item 'proto' field.
411 The last extension header item 'next header' field can specify the following
412 header protocol type.
416 - 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.
417 - Hairpin in switchdev SR-IOV mode is not supported till now.
421 - All the meter colors with drop action will be counted only by the global drop statistics.
422 - Green color is not supported with drop action.
423 - Yellow detection is not supported.
424 - Red color must be with drop action.
425 - Meter statistics are supported only for drop case.
426 - Meter yellow color detection is not supported.
427 - A meter action created with pre-defined policy must be the last action in the flow except single case where the policy actions are:
428 - green: NULL or END.
429 - yellow: NULL or END.
431 - The only supported meter policy actions:
432 - green: QUEUE, RSS, PORT_ID, JUMP, MARK and SET_TAG.
433 - yellow: must be empty.
435 - meter profile packet mode is supported.
439 - Integrity offload is enabled for **ConnectX-6** family.
440 - Verification bits provided by the hardware are ``l3_ok``, ``ipv4_csum_ok``, ``l4_ok``, ``l4_csum_ok``.
441 - ``level`` value 0 references outer headers.
442 - Multiple integrity items not supported in a single flow rule.
443 - Flow rule items supplied by application must explicitly specify network headers referred by integrity item.
444 For example, if integrity item mask sets ``l4_ok`` or ``l4_csum_ok`` bits, reference to L4 network header,
445 TCP or UDP, must be in the rule pattern as well::
447 flow create 0 ingress pattern integrity level is 0 value mask l3_ok value spec l3_ok / eth / ipv6 / end …
449 flow create 0 ingress pattern integrity level is 0 value mask l4_ok value spec 0 / eth / ipv4 proto is udp / end …
451 - Connection tracking:
453 - Cannot co-exist with ASO meter, ASO age action in a single flow rule.
454 - Flow rules insertion rate and memory consumption need more optimization.
456 - 4M connections maximum.
458 - Multi-thread flow insertion:
460 - In order to achieve best insertion rate, application should manage the flows per lcore.
461 - Better to disable memory reclaim by setting ``reclaim_mem_mode`` to 0 to accelerate the flow object allocation and release with cache.
466 MLX5 supports various methods to report statistics:
468 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.
470 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.
472 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.
480 The ibverbs libraries can be linked with this PMD in a number of ways,
481 configured by the ``ibverbs_link`` build option:
483 - ``shared`` (default): the PMD depends on some .so files.
485 - ``dlopen``: Split the dependencies glue in a separate library
486 loaded when needed by dlopen.
487 It make dependencies on libibverbs and libmlx4 optional,
488 and has no performance impact.
490 - ``static``: Embed static flavor of the dependencies libibverbs and libmlx4
491 in the PMD shared library or the executable static binary.
493 Environment variables
494 ~~~~~~~~~~~~~~~~~~~~~
498 A list of directories in which to search for the rdma-core "glue" plug-in,
499 separated by colons or semi-colons.
501 - ``MLX5_SHUT_UP_BF``
503 Configures HW Tx doorbell register as IO-mapped.
505 By default, the HW Tx doorbell is configured as a write-combining register.
506 The register would be flushed to HW usually when the write-combining buffer
507 becomes full, but it depends on CPU design.
509 Except for vectorized Tx burst routines, a write memory barrier is enforced
510 after updating the register so that the update can be immediately visible to
513 When vectorized Tx burst is called, the barrier is set only if the burst size
514 is not aligned to MLX5_VPMD_TX_MAX_BURST. However, setting this environmental
515 variable will bring better latency even though the maximum throughput can
518 Run-time configuration
519 ~~~~~~~~~~~~~~~~~~~~~~
521 - librte_net_mlx5 brings kernel network interfaces up during initialization
522 because it is affected by their state. Forcing them down prevents packets
525 - **ethtool** operations on related kernel interfaces also affect the PMD.
530 In order to run as a non-root user,
531 some capabilities must be granted to the application::
533 setcap cap_sys_admin,cap_net_admin,cap_net_raw,cap_ipc_lock+ep <dpdk-app>
535 Below are the reasons of the need for each capability:
538 When using physical addresses (PA mode), with Linux >= 4.0,
539 for access to ``/proc/self/pagemap``.
542 For device configuration.
545 For raw ethernet queue allocation through kernel driver.
548 For DMA memory pinning.
553 - ``rxq_cqe_comp_en`` parameter [int]
555 A nonzero value enables the compression of CQE on RX side. This feature
556 allows to save PCI bandwidth and improve performance. Enabled by default.
557 Different compression formats are supported in order to achieve the best
558 performance for different traffic patterns. Default format depends on
559 Multi-Packet Rx queue configuration: Hash RSS format is used in case
560 MPRQ is disabled, Checksum format is used in case MPRQ is enabled.
562 Specifying 2 as a ``rxq_cqe_comp_en`` value selects Flow Tag format for
563 better compression rate in case of RTE Flow Mark traffic.
564 Specifying 3 as a ``rxq_cqe_comp_en`` value selects Checksum format.
565 Specifying 4 as a ``rxq_cqe_comp_en`` value selects L3/L4 Header format for
566 better compression rate in case of mixed TCP/UDP and IPv4/IPv6 traffic.
567 CQE compression format selection requires DevX to be enabled. If there is
568 no DevX enabled/supported the value is reset to 1 by default.
572 - x86_64 with ConnectX-4, ConnectX-4 Lx, ConnectX-5, ConnectX-6, ConnectX-6 Dx,
573 ConnectX-6 Lx, BlueField and BlueField-2.
574 - POWER9 and ARMv8 with ConnectX-4 Lx, ConnectX-5, ConnectX-6, ConnectX-6 Dx,
575 ConnectX-6 Lx, BlueField and BlueField-2.
577 - ``rxq_pkt_pad_en`` parameter [int]
579 A nonzero value enables padding Rx packet to the size of cacheline on PCI
580 transaction. This feature would waste PCI bandwidth but could improve
581 performance by avoiding partial cacheline write which may cause costly
582 read-modify-copy in memory transaction on some architectures. Disabled by
587 - x86_64 with ConnectX-4, ConnectX-4 Lx, ConnectX-5, ConnectX-6, ConnectX-6 Dx,
588 ConnectX-6 Lx, BlueField and BlueField-2.
589 - POWER8 and ARMv8 with ConnectX-4 Lx, ConnectX-5, ConnectX-6, ConnectX-6 Dx,
590 ConnectX-6 Lx, BlueField and BlueField-2.
592 - ``mprq_en`` parameter [int]
594 A nonzero value enables configuring Multi-Packet Rx queues. Rx queue is
595 configured as Multi-Packet RQ if the total number of Rx queues is
596 ``rxqs_min_mprq`` or more. Disabled by default.
598 Multi-Packet Rx Queue (MPRQ a.k.a Striding RQ) can further save PCIe bandwidth
599 by posting a single large buffer for multiple packets. Instead of posting a
600 buffers per a packet, one large buffer is posted in order to receive multiple
601 packets on the buffer. A MPRQ buffer consists of multiple fixed-size strides
602 and each stride receives one packet. MPRQ can improve throughput for
603 small-packet traffic.
605 When MPRQ is enabled, max_rx_pkt_len can be larger than the size of
606 user-provided mbuf even if DEV_RX_OFFLOAD_SCATTER isn't enabled. PMD will
607 configure large stride size enough to accommodate max_rx_pkt_len as long as
608 device allows. Note that this can waste system memory compared to enabling Rx
609 scatter and multi-segment packet.
611 - ``mprq_log_stride_num`` parameter [int]
613 Log 2 of the number of strides for Multi-Packet Rx queue. Configuring more
614 strides can reduce PCIe traffic further. If configured value is not in the
615 range of device capability, the default value will be set with a warning
616 message. The default value is 4 which is 16 strides per a buffer, valid only
617 if ``mprq_en`` is set.
619 The size of Rx queue should be bigger than the number of strides.
621 - ``mprq_log_stride_size`` parameter [int]
623 Log 2 of the size of a stride for Multi-Packet Rx queue. Configuring a smaller
624 stride size can save some memory and reduce probability of a depletion of all
625 available strides due to unreleased packets by an application. If configured
626 value is not in the range of device capability, the default value will be set
627 with a warning message. The default value is 11 which is 2048 bytes per a
628 stride, valid only if ``mprq_en`` is set. With ``mprq_log_stride_size`` set
629 it is possible for a packet to span across multiple strides. This mode allows
630 support of jumbo frames (9K) with MPRQ. The memcopy of some packets (or part
631 of a packet if Rx scatter is configured) may be required in case there is no
632 space left for a head room at the end of a stride which incurs some
635 - ``mprq_max_memcpy_len`` parameter [int]
637 The maximum length of packet to memcpy in case of Multi-Packet Rx queue. Rx
638 packet is mem-copied to a user-provided mbuf if the size of Rx packet is less
639 than or equal to this parameter. Otherwise, PMD will attach the Rx packet to
640 the mbuf by external buffer attachment - ``rte_pktmbuf_attach_extbuf()``.
641 A mempool for external buffers will be allocated and managed by PMD. If Rx
642 packet is externally attached, ol_flags field of the mbuf will have
643 EXT_ATTACHED_MBUF and this flag must be preserved. ``RTE_MBUF_HAS_EXTBUF()``
644 checks the flag. The default value is 128, valid only if ``mprq_en`` is set.
646 - ``rxqs_min_mprq`` parameter [int]
648 Configure Rx queues as Multi-Packet RQ if the total number of Rx queues is
649 greater or equal to this value. The default value is 12, valid only if
652 - ``txq_inline`` parameter [int]
654 Amount of data to be inlined during TX operations. This parameter is
655 deprecated and converted to the new parameter ``txq_inline_max`` providing
656 partial compatibility.
658 - ``txqs_min_inline`` parameter [int]
660 Enable inline data send only when the number of TX queues is greater or equal
663 This option should be used in combination with ``txq_inline_max`` and
664 ``txq_inline_mpw`` below and does not affect ``txq_inline_min`` settings above.
666 If this option is not specified the default value 16 is used for BlueField
667 and 8 for other platforms
669 The data inlining consumes the CPU cycles, so this option is intended to
670 auto enable inline data if we have enough Tx queues, which means we have
671 enough CPU cores and PCI bandwidth is getting more critical and CPU
672 is not supposed to be bottleneck anymore.
674 The copying data into WQE improves latency and can improve PPS performance
675 when PCI back pressure is detected and may be useful for scenarios involving
676 heavy traffic on many queues.
678 Because additional software logic is necessary to handle this mode, this
679 option should be used with care, as it may lower performance when back
680 pressure is not expected.
682 If inline data are enabled it may affect the maximal size of Tx queue in
683 descriptors because the inline data increase the descriptor size and
684 queue size limits supported by hardware may be exceeded.
686 - ``txq_inline_min`` parameter [int]
688 Minimal amount of data to be inlined into WQE during Tx operations. NICs
689 may require this minimal data amount to operate correctly. The exact value
690 may depend on NIC operation mode, requested offloads, etc. It is strongly
691 recommended to omit this parameter and use the default values. Anyway,
692 applications using this parameter should take into consideration that
693 specifying an inconsistent value may prevent the NIC from sending packets.
695 If ``txq_inline_min`` key is present the specified value (may be aligned
696 by the driver in order not to exceed the limits and provide better descriptor
697 space utilization) will be used by the driver and it is guaranteed that
698 requested amount of data bytes are inlined into the WQE beside other inline
699 settings. This key also may update ``txq_inline_max`` value (default
700 or specified explicitly in devargs) to reserve the space for inline data.
702 If ``txq_inline_min`` key is not present, the value may be queried by the
703 driver from the NIC via DevX if this feature is available. If there is no DevX
704 enabled/supported the value 18 (supposing L2 header including VLAN) is set
705 for ConnectX-4 and ConnectX-4 Lx, and 0 is set by default for ConnectX-5
706 and newer NICs. If packet is shorter the ``txq_inline_min`` value, the entire
709 For ConnectX-4 NIC, driver does not allow specifying value below 18
710 (minimal L2 header, including VLAN), error will be raised.
712 For ConnectX-4 Lx NIC, it is allowed to specify values below 18, but
713 it is not recommended and may prevent NIC from sending packets over
716 For ConnectX-4 and ConnectX-4 Lx NICs, automatically configured value
717 is insufficient for some traffic, because they require at least all L2 headers
718 to be inlined. For example, Q-in-Q adds 4 bytes to default 18 bytes
719 of Ethernet and VLAN, thus ``txq_inline_min`` must be set to 22.
720 MPLS would add 4 bytes per label. Final value must account for all possible
721 L2 encapsulation headers used in particular environment.
723 Please, note, this minimal data inlining disengages eMPW feature (Enhanced
724 Multi-Packet Write), because last one does not support partial packet inlining.
725 This is not very critical due to minimal data inlining is mostly required
726 by ConnectX-4 and ConnectX-4 Lx, these NICs do not support eMPW feature.
728 - ``txq_inline_max`` parameter [int]
730 Specifies the maximal packet length to be completely inlined into WQE
731 Ethernet Segment for ordinary SEND method. If packet is larger than specified
732 value, the packet data won't be copied by the driver at all, data buffer
733 is addressed with a pointer. If packet length is less or equal all packet
734 data will be copied into WQE. This may improve PCI bandwidth utilization for
735 short packets significantly but requires the extra CPU cycles.
737 The data inline feature is controlled by number of Tx queues, if number of Tx
738 queues is larger than ``txqs_min_inline`` key parameter, the inline feature
739 is engaged, if there are not enough Tx queues (which means not enough CPU cores
740 and CPU resources are scarce), data inline is not performed by the driver.
741 Assigning ``txqs_min_inline`` with zero always enables the data inline.
743 The default ``txq_inline_max`` value is 290. The specified value may be adjusted
744 by the driver in order not to exceed the limit (930 bytes) and to provide better
745 WQE space filling without gaps, the adjustment is reflected in the debug log.
746 Also, the default value (290) may be decreased in run-time if the large transmit
747 queue size is requested and hardware does not support enough descriptor
748 amount, in this case warning is emitted. If ``txq_inline_max`` key is
749 specified and requested inline settings can not be satisfied then error
752 - ``txq_inline_mpw`` parameter [int]
754 Specifies the maximal packet length to be completely inlined into WQE for
755 Enhanced MPW method. If packet is large the specified value, the packet data
756 won't be copied, and data buffer is addressed with pointer. If packet length
757 is less or equal, all packet data will be copied into WQE. This may improve PCI
758 bandwidth utilization for short packets significantly but requires the extra
761 The data inline feature is controlled by number of TX queues, if number of Tx
762 queues is larger than ``txqs_min_inline`` key parameter, the inline feature
763 is engaged, if there are not enough Tx queues (which means not enough CPU cores
764 and CPU resources are scarce), data inline is not performed by the driver.
765 Assigning ``txqs_min_inline`` with zero always enables the data inline.
767 The default ``txq_inline_mpw`` value is 268. The specified value may be adjusted
768 by the driver in order not to exceed the limit (930 bytes) and to provide better
769 WQE space filling without gaps, the adjustment is reflected in the debug log.
770 Due to multiple packets may be included to the same WQE with Enhanced Multi
771 Packet Write Method and overall WQE size is limited it is not recommended to
772 specify large values for the ``txq_inline_mpw``. Also, the default value (268)
773 may be decreased in run-time if the large transmit queue size is requested
774 and hardware does not support enough descriptor amount, in this case warning
775 is emitted. If ``txq_inline_mpw`` key is specified and requested inline
776 settings can not be satisfied then error will be raised.
778 - ``txqs_max_vec`` parameter [int]
780 Enable vectorized Tx only when the number of TX queues is less than or
781 equal to this value. This parameter is deprecated and ignored, kept
782 for compatibility issue to not prevent driver from probing.
784 - ``txq_mpw_hdr_dseg_en`` parameter [int]
786 A nonzero value enables including two pointers in the first block of TX
787 descriptor. The parameter is deprecated and ignored, kept for compatibility
790 - ``txq_max_inline_len`` parameter [int]
792 Maximum size of packet to be inlined. This limits the size of packet to
793 be inlined. If the size of a packet is larger than configured value, the
794 packet isn't inlined even though there's enough space remained in the
795 descriptor. Instead, the packet is included with pointer. This parameter
796 is deprecated and converted directly to ``txq_inline_mpw`` providing full
797 compatibility. Valid only if eMPW feature is engaged.
799 - ``txq_mpw_en`` parameter [int]
801 A nonzero value enables Enhanced Multi-Packet Write (eMPW) for ConnectX-5,
802 ConnectX-6, ConnectX-6 Dx, ConnectX-6 Lx, BlueField, BlueField-2.
803 eMPW allows the Tx burst function to pack up multiple packets
804 in a single descriptor session in order to save PCI bandwidth
805 and improve performance at the cost of a slightly higher CPU usage.
806 When ``txq_inline_mpw`` is set along with ``txq_mpw_en``,
807 Tx burst function copies entire packet data on to Tx descriptor
808 instead of including pointer of packet.
810 The Enhanced Multi-Packet Write feature is enabled by default if NIC supports
811 it, can be disabled by explicit specifying 0 value for ``txq_mpw_en`` option.
812 Also, if minimal data inlining is requested by non-zero ``txq_inline_min``
813 option or reported by the NIC, the eMPW feature is disengaged.
815 - ``tx_db_nc`` parameter [int]
817 The rdma core library can map doorbell register in two ways, depending on the
818 environment variable "MLX5_SHUT_UP_BF":
820 - As regular cached memory (usually with write combining attribute), if the
821 variable is either missing or set to zero.
822 - As non-cached memory, if the variable is present and set to not "0" value.
824 The type of mapping may slightly affect the Tx performance, the optimal choice
825 is strongly relied on the host architecture and should be deduced practically.
827 If ``tx_db_nc`` is set to zero, the doorbell is forced to be mapped to regular
828 memory (with write combining), the PMD will perform the extra write memory barrier
829 after writing to doorbell, it might increase the needed CPU clocks per packet
830 to send, but latency might be improved.
832 If ``tx_db_nc`` is set to one, the doorbell is forced to be mapped to non
833 cached memory, the PMD will not perform the extra write memory barrier
834 after writing to doorbell, on some architectures it might improve the
837 If ``tx_db_nc`` is set to two, the doorbell is forced to be mapped to regular
838 memory, the PMD will use heuristics to decide whether write memory barrier
839 should be performed. For bursts with size multiple of recommended one (64 pkts)
840 it is supposed the next burst is coming and no need to issue the extra memory
841 barrier (it is supposed to be issued in the next coming burst, at least after
842 descriptor writing). It might increase latency (on some hosts till next
843 packets transmit) and should be used with care.
845 If ``tx_db_nc`` is omitted or set to zero, the preset (if any) environment
846 variable "MLX5_SHUT_UP_BF" value is used. If there is no "MLX5_SHUT_UP_BF",
847 the default ``tx_db_nc`` value is zero for ARM64 hosts and one for others.
849 - ``tx_pp`` parameter [int]
851 If a nonzero value is specified the driver creates all necessary internal
852 objects to provide accurate packet send scheduling on mbuf timestamps.
853 The positive value specifies the scheduling granularity in nanoseconds,
854 the packet send will be accurate up to specified digits. The allowed range is
855 from 500 to 1 million of nanoseconds. The negative value specifies the module
856 of granularity and engages the special test mode the check the schedule rate.
857 By default (if the ``tx_pp`` is not specified) send scheduling on timestamps
860 - ``tx_skew`` parameter [int]
862 The parameter adjusts the send packet scheduling on timestamps and represents
863 the average delay between beginning of the transmitting descriptor processing
864 by the hardware and appearance of actual packet data on the wire. The value
865 should be provided in nanoseconds and is valid only if ``tx_pp`` parameter is
866 specified. The default value is zero.
868 - ``tx_vec_en`` parameter [int]
870 A nonzero value enables Tx vector on ConnectX-5, ConnectX-6, ConnectX-6 Dx,
871 ConnectX-6 Lx, BlueField and BlueField-2 NICs
872 if the number of global Tx queues on the port is less than ``txqs_max_vec``.
873 The parameter is deprecated and ignored.
875 - ``rx_vec_en`` parameter [int]
877 A nonzero value enables Rx vector if the port is not configured in
878 multi-segment otherwise this parameter is ignored.
882 - ``vf_nl_en`` parameter [int]
884 A nonzero value enables Netlink requests from the VF to add/remove MAC
885 addresses or/and enable/disable promiscuous/all multicast on the Netdevice.
886 Otherwise the relevant configuration must be run with Linux iproute2 tools.
887 This is a prerequisite to receive this kind of traffic.
889 Enabled by default, valid only on VF devices ignored otherwise.
891 - ``l3_vxlan_en`` parameter [int]
893 A nonzero value allows L3 VXLAN and VXLAN-GPE flow creation. To enable
894 L3 VXLAN or VXLAN-GPE, users has to configure firmware and enable this
895 parameter. This is a prerequisite to receive this kind of traffic.
899 - ``dv_xmeta_en`` parameter [int]
901 A nonzero value enables extensive flow metadata support if device is
902 capable and driver supports it. This can enable extensive support of
903 ``MARK`` and ``META`` item of ``rte_flow``. The newly introduced
904 ``SET_TAG`` and ``SET_META`` actions do not depend on ``dv_xmeta_en``.
906 There are some possible configurations, depending on parameter value:
908 - 0, this is default value, defines the legacy mode, the ``MARK`` and
909 ``META`` related actions and items operate only within NIC Tx and
910 NIC Rx steering domains, no ``MARK`` and ``META`` information crosses
911 the domain boundaries. The ``MARK`` item is 24 bits wide, the ``META``
912 item is 32 bits wide and match supported on egress only.
914 - 1, this engages extensive metadata mode, the ``MARK`` and ``META``
915 related actions and items operate within all supported steering domains,
916 including FDB, ``MARK`` and ``META`` information may cross the domain
917 boundaries. The ``MARK`` item is 24 bits wide, the ``META`` item width
918 depends on kernel and firmware configurations and might be 0, 16 or
919 32 bits. Within NIC Tx domain ``META`` data width is 32 bits for
920 compatibility, the actual width of data transferred to the FDB domain
921 depends on kernel configuration and may be vary. The actual supported
922 width can be retrieved in runtime by series of rte_flow_validate()
925 - 2, this engages extensive metadata mode, the ``MARK`` and ``META``
926 related actions and items operate within all supported steering domains,
927 including FDB, ``MARK`` and ``META`` information may cross the domain
928 boundaries. The ``META`` item is 32 bits wide, the ``MARK`` item width
929 depends on kernel and firmware configurations and might be 0, 16 or
930 24 bits. The actual supported width can be retrieved in runtime by
931 series of rte_flow_validate() trials.
933 - 3, this engages tunnel offload mode. In E-Switch configuration, that
934 mode implicitly activates ``dv_xmeta_en=1``.
936 +------+-----------+-----------+-------------+-------------+
937 | Mode | ``MARK`` | ``META`` | ``META`` Tx | FDB/Through |
938 +======+===========+===========+=============+=============+
939 | 0 | 24 bits | 32 bits | 32 bits | no |
940 +------+-----------+-----------+-------------+-------------+
941 | 1 | 24 bits | vary 0-32 | 32 bits | yes |
942 +------+-----------+-----------+-------------+-------------+
943 | 2 | vary 0-24 | 32 bits | 32 bits | yes |
944 +------+-----------+-----------+-------------+-------------+
946 If there is no E-Switch configuration the ``dv_xmeta_en`` parameter is
947 ignored and the device is configured to operate in legacy mode (0).
949 Disabled by default (set to 0).
951 The Direct Verbs/Rules (engaged with ``dv_flow_en`` = 1) supports all
952 of the extensive metadata features. The legacy Verbs supports FLAG and
953 MARK metadata actions over NIC Rx steering domain only.
955 Setting META value to zero in flow action means there is no item provided
956 and receiving datapath will not report in mbufs the metadata are present.
957 Setting MARK value to zero in flow action means the zero FDIR ID value
958 will be reported on packet receiving.
960 For the MARK action the last 16 values in the full range are reserved for
961 internal PMD purposes (to emulate FLAG action). The valid range for the
962 MARK action values is 0-0xFFEF for the 16-bit mode and 0-xFFFFEF
963 for the 24-bit mode, the flows with the MARK action value outside
964 the specified range will be rejected.
966 - ``dv_flow_en`` parameter [int]
968 A nonzero value enables the DV flow steering assuming it is supported
969 by the driver (RDMA Core library version is rdma-core-24.0 or higher).
971 Enabled by default if supported.
973 - ``dv_esw_en`` parameter [int]
975 A nonzero value enables E-Switch using Direct Rules.
977 Enabled by default if supported.
979 - ``lacp_by_user`` parameter [int]
981 A nonzero value enables the control of LACP traffic by the user application.
982 When a bond exists in the driver, by default it should be managed by the
983 kernel and therefore LACP traffic should be steered to the kernel.
984 If this devarg is set to 1 it will allow the user to manage the bond by
985 itself and not steer LACP traffic to the kernel.
987 Disabled by default (set to 0).
989 - ``mr_ext_memseg_en`` parameter [int]
991 A nonzero value enables extending memseg when registering DMA memory. If
992 enabled, the number of entries in MR (Memory Region) lookup table on datapath
993 is minimized and it benefits performance. On the other hand, it worsens memory
994 utilization because registered memory is pinned by kernel driver. Even if a
995 page in the extended chunk is freed, that doesn't become reusable until the
996 entire memory is freed.
1000 - ``representor`` parameter [list]
1002 This parameter can be used to instantiate DPDK Ethernet devices from
1003 existing port (PF, VF or SF) representors configured on the device.
1005 It is a standard parameter whose format is described in
1006 :ref:`ethernet_device_standard_device_arguments`.
1008 For instance, to probe VF port representors 0 through 2::
1010 <PCI_BDF>,representor=vf[0-2]
1012 To probe SF port representors 0 through 2::
1014 <PCI_BDF>,representor=sf[0-2]
1016 To probe VF port representors 0 through 2 on both PFs of bonding device::
1018 <Primary_PCI_BDF>,representor=pf[0,1]vf[0-2]
1020 - ``max_dump_files_num`` parameter [int]
1022 The maximum number of files per PMD entity that may be created for debug information.
1023 The files will be created in /var/log directory or in current directory.
1025 set to 128 by default.
1027 - ``lro_timeout_usec`` parameter [int]
1029 The maximum allowed duration of an LRO session, in micro-seconds.
1030 PMD will set the nearest value supported by HW, which is not bigger than
1031 the input ``lro_timeout_usec`` value.
1032 If this parameter is not specified, by default PMD will set
1033 the smallest value supported by HW.
1035 - ``hp_buf_log_sz`` parameter [int]
1037 The total data buffer size of a hairpin queue (logarithmic form), in bytes.
1038 PMD will set the data buffer size to 2 ** ``hp_buf_log_sz``, both for RX & TX.
1039 The capacity of the value is specified by the firmware and the initialization
1040 will get a failure if it is out of scope.
1041 The range of the value is from 11 to 19 right now, and the supported frame
1042 size of a single packet for hairpin is from 512B to 128KB. It might change if
1043 different firmware release is being used. By using a small value, it could
1044 reduce memory consumption but not work with a large frame. If the value is
1045 too large, the memory consumption will be high and some potential performance
1046 degradation will be introduced.
1047 By default, the PMD will set this value to 16, which means that 9KB jumbo
1048 frames will be supported.
1050 - ``reclaim_mem_mode`` parameter [int]
1052 Cache some resources in flow destroy will help flow recreation more efficient.
1053 While some systems may require the all the resources can be reclaimed after
1055 The parameter ``reclaim_mem_mode`` provides the option for user to configure
1056 if the resource cache is needed or not.
1058 There are three options to choose:
1060 - 0. It means the flow resources will be cached as usual. The resources will
1061 be cached, helpful with flow insertion rate.
1063 - 1. It will only enable the DPDK PMD level resources reclaim.
1065 - 2. Both DPDK PMD level and rdma-core low level will be configured as
1068 By default, the PMD will set this value to 0.
1070 - ``sys_mem_en`` parameter [int]
1072 A non-zero value enables the PMD memory management allocating memory
1073 from system by default, without explicit rte memory flag.
1075 By default, the PMD will set this value to 0.
1077 - ``decap_en`` parameter [int]
1079 Some devices do not support FCS (frame checksum) scattering for
1080 tunnel-decapsulated packets.
1081 If set to 0, this option forces the FCS feature and rejects tunnel
1082 decapsulation in the flow engine for such devices.
1084 By default, the PMD will set this value to 1.
1086 - ``allow_duplicate_pattern`` parameter [int]
1088 There are two options to choose:
1090 - 0. Prevent insertion of rules with the same pattern items on non-root table.
1091 In this case, only the first rule is inserted and the following rules are
1092 rejected and error code EEXIST is returned.
1094 - 1. Allow insertion of rules with the same pattern items.
1095 In this case, all rules are inserted but only the first rule takes effect,
1096 the next rule takes effect only if the previous rules are deleted.
1098 By default, the PMD will set this value to 1.
1100 .. _mlx5_firmware_config:
1102 Firmware configuration
1103 ~~~~~~~~~~~~~~~~~~~~~~
1105 Firmware features can be configured as key/value pairs.
1107 The command to set a value is::
1109 mlxconfig -d <device> set <key>=<value>
1111 The command to query a value is::
1113 mlxconfig -d <device> query | grep <key>
1115 The device name for the command ``mlxconfig`` can be either the PCI address,
1116 or the mst device name found with::
1120 Below are some firmware configurations listed.
1126 value: 1=Infiniband 2=Ethernet 3=VPI(auto-sense)
1132 - maximum number of SR-IOV virtual functions::
1136 - enable DevX (required by Direct Rules and other features)::
1140 - aggressive CQE zipping::
1144 - L3 VXLAN and VXLAN-GPE destination UDP port::
1147 IP_OVER_VXLAN_PORT=<udp dport>
1149 - enable VXLAN-GPE tunnel flow matching::
1151 FLEX_PARSER_PROFILE_ENABLE=0
1153 FLEX_PARSER_PROFILE_ENABLE=2
1155 - enable IP-in-IP tunnel flow matching::
1157 FLEX_PARSER_PROFILE_ENABLE=0
1159 - enable MPLS flow matching::
1161 FLEX_PARSER_PROFILE_ENABLE=1
1163 - enable ICMP(code/type/identifier/sequence number) / ICMP6(code/type) fields matching::
1165 FLEX_PARSER_PROFILE_ENABLE=2
1167 - enable Geneve flow matching::
1169 FLEX_PARSER_PROFILE_ENABLE=0
1171 FLEX_PARSER_PROFILE_ENABLE=1
1173 - enable Geneve TLV option flow matching::
1175 FLEX_PARSER_PROFILE_ENABLE=0
1177 - enable GTP flow matching::
1179 FLEX_PARSER_PROFILE_ENABLE=3
1181 - enable eCPRI flow matching::
1183 FLEX_PARSER_PROFILE_ENABLE=4
1189 This driver relies on external libraries and kernel drivers for resources
1190 allocations and initialization. The following dependencies are not part of
1191 DPDK and must be installed separately:
1195 User space Verbs framework used by librte_net_mlx5. This library provides
1196 a generic interface between the kernel and low-level user space drivers
1199 It allows slow and privileged operations (context initialization, hardware
1200 resources allocations) to be managed by the kernel and fast operations to
1201 never leave user space.
1205 Low-level user space driver library for Mellanox
1206 ConnectX-4/ConnectX-5/ConnectX-6/BlueField devices, it is automatically loaded
1209 This library basically implements send/receive calls to the hardware
1212 - **Kernel modules**
1214 They provide the kernel-side Verbs API and low level device drivers that
1215 manage actual hardware initialization and resources sharing with user
1218 Unlike most other PMDs, these modules must remain loaded and bound to
1221 - mlx5_core: hardware driver managing Mellanox
1222 ConnectX-4/ConnectX-5/ConnectX-6/BlueField devices and related Ethernet kernel
1224 - mlx5_ib: InifiniBand device driver.
1225 - ib_uverbs: user space driver for Verbs (entry point for libibverbs).
1227 - **Firmware update**
1229 Mellanox OFED/EN releases include firmware updates for
1230 ConnectX-4/ConnectX-5/ConnectX-6/BlueField adapters.
1232 Because each release provides new features, these updates must be applied to
1233 match the kernel modules and libraries they come with.
1237 Both libraries are BSD and GPL licensed. Linux kernel modules are GPL
1243 Either RDMA Core library with a recent enough Linux kernel release
1244 (recommended) or Mellanox OFED/EN, which provides compatibility with older
1247 RDMA Core with Linux Kernel
1248 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
1250 - Minimal kernel version : v4.14 or the most recent 4.14-rc (see `Linux installation documentation`_)
1251 - Minimal rdma-core version: v15+ commit 0c5f5765213a ("Merge pull request #227 from yishaih/tm")
1252 (see `RDMA Core installation documentation`_)
1253 - When building for i686 use:
1255 - rdma-core version 18.0 or above built with 32bit support.
1256 - Kernel version 4.14.41 or above.
1258 - Starting with rdma-core v21, static libraries can be built::
1261 CFLAGS=-fPIC cmake -DIN_PLACE=1 -DENABLE_STATIC=1 -GNinja ..
1264 .. _`Linux installation documentation`: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/plain/Documentation/admin-guide/README.rst
1265 .. _`RDMA Core installation documentation`: https://raw.githubusercontent.com/linux-rdma/rdma-core/master/README.md
1271 - Mellanox OFED version: **4.5** and above /
1272 Mellanox EN version: **4.5** and above
1275 - ConnectX-4: **12.21.1000** and above.
1276 - ConnectX-4 Lx: **14.21.1000** and above.
1277 - ConnectX-5: **16.21.1000** and above.
1278 - ConnectX-5 Ex: **16.21.1000** and above.
1279 - ConnectX-6: **20.27.0090** and above.
1280 - ConnectX-6 Dx: **22.27.0090** and above.
1281 - BlueField: **18.25.1010** and above.
1283 While these libraries and kernel modules are available on OpenFabrics
1284 Alliance's `website <https://www.openfabrics.org/>`__ and provided by package
1285 managers on most distributions, this PMD requires Ethernet extensions that
1286 may not be supported at the moment (this is a work in progress).
1289 <http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux>`__ and
1291 <http://www.mellanox.com/page/products_dyn?product_family=27&mtag=linux>`__
1292 include the necessary support and should be used in the meantime. For DPDK,
1293 only libibverbs, libmlx5, mlnx-ofed-kernel packages and firmware updates are
1294 required from that distribution.
1298 Several versions of Mellanox OFED/EN are available. Installing the version
1299 this DPDK release was developed and tested against is strongly
1300 recommended. Please check the `linux prerequisites`_.
1302 Windows Prerequisites
1303 ---------------------
1305 This driver relies on external libraries and kernel drivers for resources
1306 allocations and initialization. The dependencies in the following sub-sections
1307 are not part of DPDK, and must be installed separately.
1309 Compilation Prerequisites
1310 ~~~~~~~~~~~~~~~~~~~~~~~~~
1312 DevX SDK installation
1313 ^^^^^^^^^^^^^^^^^^^^^
1315 The DevX SDK must be installed on the machine building the Windows PMD.
1316 Additional information can be found at
1317 `How to Integrate Windows DevX in Your Development Environment
1318 <https://docs.mellanox.com/display/winof2v250/RShim+Drivers+and+Usage#RShimDriversandUsage-DevXInterface>`__.
1320 Runtime Prerequisites
1321 ~~~~~~~~~~~~~~~~~~~~~
1323 WinOF2 version 2.60 or higher must be installed on the machine.
1328 The driver can be downloaded from the following site:
1330 <https://www.mellanox.com/products/adapter-software/ethernet/windows/winof-2>`__
1335 DevX for Windows must be enabled in the Windows registry.
1336 The keys ``DevxEnabled`` and ``DevxFsRules`` must be set.
1337 Additional information can be found in the WinOF2 user manual.
1342 The following Mellanox device families are supported by the same mlx5 driver:
1354 Below are detailed device names:
1356 * Mellanox\ |reg| ConnectX\ |reg|-4 10G MCX4111A-XCAT (1x10G)
1357 * Mellanox\ |reg| ConnectX\ |reg|-4 10G MCX412A-XCAT (2x10G)
1358 * Mellanox\ |reg| ConnectX\ |reg|-4 25G MCX4111A-ACAT (1x25G)
1359 * Mellanox\ |reg| ConnectX\ |reg|-4 25G MCX412A-ACAT (2x25G)
1360 * Mellanox\ |reg| ConnectX\ |reg|-4 40G MCX413A-BCAT (1x40G)
1361 * Mellanox\ |reg| ConnectX\ |reg|-4 40G MCX4131A-BCAT (1x40G)
1362 * Mellanox\ |reg| ConnectX\ |reg|-4 40G MCX415A-BCAT (1x40G)
1363 * Mellanox\ |reg| ConnectX\ |reg|-4 50G MCX413A-GCAT (1x50G)
1364 * Mellanox\ |reg| ConnectX\ |reg|-4 50G MCX4131A-GCAT (1x50G)
1365 * Mellanox\ |reg| ConnectX\ |reg|-4 50G MCX414A-BCAT (2x50G)
1366 * Mellanox\ |reg| ConnectX\ |reg|-4 50G MCX415A-GCAT (1x50G)
1367 * Mellanox\ |reg| ConnectX\ |reg|-4 50G MCX416A-BCAT (2x50G)
1368 * Mellanox\ |reg| ConnectX\ |reg|-4 50G MCX416A-GCAT (2x50G)
1369 * Mellanox\ |reg| ConnectX\ |reg|-4 50G MCX415A-CCAT (1x100G)
1370 * Mellanox\ |reg| ConnectX\ |reg|-4 100G MCX416A-CCAT (2x100G)
1371 * Mellanox\ |reg| ConnectX\ |reg|-4 Lx 10G MCX4111A-XCAT (1x10G)
1372 * Mellanox\ |reg| ConnectX\ |reg|-4 Lx 10G MCX4121A-XCAT (2x10G)
1373 * Mellanox\ |reg| ConnectX\ |reg|-4 Lx 25G MCX4111A-ACAT (1x25G)
1374 * Mellanox\ |reg| ConnectX\ |reg|-4 Lx 25G MCX4121A-ACAT (2x25G)
1375 * Mellanox\ |reg| ConnectX\ |reg|-4 Lx 40G MCX4131A-BCAT (1x40G)
1376 * Mellanox\ |reg| ConnectX\ |reg|-5 100G MCX556A-ECAT (2x100G)
1377 * Mellanox\ |reg| ConnectX\ |reg|-5 Ex EN 100G MCX516A-CDAT (2x100G)
1378 * Mellanox\ |reg| ConnectX\ |reg|-6 200G MCX654106A-HCAT (2x200G)
1379 * Mellanox\ |reg| ConnectX\ |reg|-6 Dx EN 100G MCX623106AN-CDAT (2x100G)
1380 * Mellanox\ |reg| ConnectX\ |reg|-6 Dx EN 200G MCX623105AN-VDAT (1x200G)
1381 * Mellanox\ |reg| ConnectX\ |reg|-6 Lx EN 25G MCX631102AN-ADAT (2x25G)
1383 Quick Start Guide on OFED/EN
1384 ----------------------------
1386 1. Download latest Mellanox OFED/EN. For more info check the `linux prerequisites`_.
1389 2. Install the required libraries and kernel modules either by installing
1390 only the required set, or by installing the entire Mellanox OFED/EN::
1392 ./mlnxofedinstall --upstream-libs --dpdk
1394 3. Verify the firmware is the correct one::
1398 4. Verify all ports links are set to Ethernet::
1400 mlxconfig -d <mst device> query | grep LINK_TYPE
1404 Link types may have to be configured to Ethernet::
1406 mlxconfig -d <mst device> set LINK_TYPE_P1/2=1/2/3
1408 * LINK_TYPE_P1=<1|2|3> , 1=Infiniband 2=Ethernet 3=VPI(auto-sense)
1410 For hypervisors, verify SR-IOV is enabled on the NIC::
1412 mlxconfig -d <mst device> query | grep SRIOV_EN
1415 If needed, configure SR-IOV::
1417 mlxconfig -d <mst device> set SRIOV_EN=1 NUM_OF_VFS=16
1418 mlxfwreset -d <mst device> reset
1420 5. Restart the driver::
1422 /etc/init.d/openibd restart
1426 service openibd restart
1428 If link type was changed, firmware must be reset as well::
1430 mlxfwreset -d <mst device> reset
1432 For hypervisors, after reset write the sysfs number of virtual functions
1435 To dynamically instantiate a given number of virtual functions (VFs)::
1437 echo [num_vfs] > /sys/class/infiniband/mlx5_0/device/sriov_numvfs
1439 6. Install DPDK and you are ready to go.
1440 See :doc:`compilation instructions <../linux_gsg/build_dpdk>`.
1442 Enable switchdev mode
1443 ---------------------
1445 Switchdev mode is a mode in E-Switch, that binds between representor and VF or SF.
1446 Representor is a port in DPDK that is connected to a VF or SF in such a way
1447 that assuming there are no offload flows, each packet that is sent from the VF or SF
1448 will be received by the corresponding representor. While each packet that is or SF
1449 sent to a representor will be received by the VF or SF.
1450 This is very useful in case of SRIOV mode, where the first packet that is sent
1451 by the VF or SF will be received by the DPDK application which will decide if this
1452 flow should be offloaded to the E-Switch. After offloading the flow packet
1453 that the VF or SF that are matching the flow will not be received any more by
1454 the DPDK application.
1456 1. Enable SRIOV mode::
1458 mlxconfig -d <mst device> set SRIOV_EN=true
1460 2. Configure the max number of VFs::
1462 mlxconfig -d <mst device> set NUM_OF_VFS=<num of vfs>
1466 mlxfwreset -d <mst device> reset
1468 3. Configure the actual number of VFs::
1470 echo <num of vfs > /sys/class/net/<net device>/device/sriov_numvfs
1472 4. Unbind the device (can be rebind after the switchdev mode)::
1474 echo -n "<device pci address" > /sys/bus/pci/drivers/mlx5_core/unbind
1476 5. Enbale switchdev mode::
1478 echo switchdev > /sys/class/net/<net device>/compat/devlink/mode
1480 Sub-Function representor
1481 ------------------------
1483 Sub-Function is a portion of the PCI device, a SF netdev has its own
1484 dedicated queues(txq, rxq). A SF netdev supports E-Switch representation
1485 offload similar to existing PF and VF representors. A SF shares PCI
1486 level resources with other SFs and/or with its parent PCI function.
1488 1. Configure SF feature::
1490 mlxconfig -d <mst device> set PF_BAR2_SIZE=<0/1/2/3> PF_BAR2_ENABLE=1
1492 Value of PF_BAR2_SIZE:
1501 mlxfwreset -d <mst device> reset
1503 3. Enable switchdev mode::
1505 echo switchdev > /sys/class/net/<net device>/compat/devlink/mode
1509 mlnx-sf -d <PCI_BDF> -a create
1511 5. Probe SF representor::
1513 testpmd> port attach <PCI_BDF>,representor=sf0,dv_flow_en=1
1518 1. Configure aggressive CQE Zipping for maximum performance::
1520 mlxconfig -d <mst device> s CQE_COMPRESSION=1
1522 To set it back to the default CQE Zipping mode use::
1524 mlxconfig -d <mst device> s CQE_COMPRESSION=0
1526 2. In case of virtualization:
1528 - Make sure that hypervisor kernel is 3.16 or newer.
1529 - Configure boot with ``iommu=pt``.
1530 - Use 1G huge pages.
1531 - Make sure to allocate a VM on huge pages.
1532 - Make sure to set CPU pinning.
1534 3. Use the CPU near local NUMA node to which the PCIe adapter is connected,
1535 for better performance. For VMs, verify that the right CPU
1536 and NUMA node are pinned according to the above. Run::
1538 lstopo-no-graphics --merge
1540 to identify the NUMA node to which the PCIe adapter is connected.
1542 4. If more than one adapter is used, and root complex capabilities allow
1543 to put both adapters on the same NUMA node without PCI bandwidth degradation,
1544 it is recommended to locate both adapters on the same NUMA node.
1545 This in order to forward packets from one to the other without
1546 NUMA performance penalty.
1548 5. Disable pause frames::
1550 ethtool -A <netdev> rx off tx off
1552 6. Verify IO non-posted prefetch is disabled by default. This can be checked
1553 via the BIOS configuration. Please contact you server provider for more
1554 information about the settings.
1558 On some machines, depends on the machine integrator, it is beneficial
1559 to set the PCI max read request parameter to 1K. This can be
1560 done in the following way:
1562 To query the read request size use::
1564 setpci -s <NIC PCI address> 68.w
1566 If the output is different than 3XXX, set it by::
1568 setpci -s <NIC PCI address> 68.w=3XXX
1570 The XXX can be different on different systems. Make sure to configure
1571 according to the setpci output.
1573 7. To minimize overhead of searching Memory Regions:
1575 - '--socket-mem' is recommended to pin memory by predictable amount.
1576 - Configure per-lcore cache when creating Mempools for packet buffer.
1577 - Refrain from dynamically allocating/freeing memory in run-time.
1582 There are multiple Rx burst functions with different advantages and limitations.
1584 .. table:: Rx burst functions
1586 +-------------------+------------------------+---------+-----------------+------+-------+
1587 || Function Name || Enabler || Scatter|| Error Recovery || CQE || Large|
1588 | | | | || comp|| MTU |
1589 +===================+========================+=========+=================+======+=======+
1590 | rx_burst | rx_vec_en=0 | Yes | Yes | Yes | Yes |
1591 +-------------------+------------------------+---------+-----------------+------+-------+
1592 | rx_burst_vec | rx_vec_en=1 (default) | No | if CQE comp off | Yes | No |
1593 +-------------------+------------------------+---------+-----------------+------+-------+
1594 | rx_burst_mprq || mprq_en=1 | No | Yes | Yes | Yes |
1595 | || RxQs >= rxqs_min_mprq | | | | |
1596 +-------------------+------------------------+---------+-----------------+------+-------+
1597 | rx_burst_mprq_vec || rx_vec_en=1 (default) | No | if CQE comp off | Yes | Yes |
1598 | || mprq_en=1 | | | | |
1599 | || RxQs >= rxqs_min_mprq | | | | |
1600 +-------------------+------------------------+---------+-----------------+------+-------+
1602 .. _mlx5_offloads_support:
1604 Supported hardware offloads
1605 ---------------------------
1607 .. table:: Minimal SW/HW versions for queue offloads
1609 ============== ===== ===== ========= ===== ========== =============
1610 Offload DPDK Linux rdma-core OFED firmware hardware
1611 ============== ===== ===== ========= ===== ========== =============
1612 common base 17.11 4.14 16 4.2-1 12.21.1000 ConnectX-4
1613 checksums 17.11 4.14 16 4.2-1 12.21.1000 ConnectX-4
1614 Rx timestamp 17.11 4.14 16 4.2-1 12.21.1000 ConnectX-4
1615 TSO 17.11 4.14 16 4.2-1 12.21.1000 ConnectX-4
1616 LRO 19.08 N/A N/A 4.6-4 16.25.6406 ConnectX-5
1617 Tx scheduling 20.08 N/A N/A 5.1-2 22.28.2006 ConnectX-6 Dx
1618 Buffer Split 20.11 N/A N/A 5.1-2 16.28.2006 ConnectX-5
1619 ============== ===== ===== ========= ===== ========== =============
1621 .. table:: Minimal SW/HW versions for rte_flow offloads
1623 +-----------------------+-----------------+-----------------+
1624 | Offload | with E-Switch | with NIC |
1625 +=======================+=================+=================+
1626 | Count | | DPDK 19.05 | | DPDK 19.02 |
1627 | | | OFED 4.6 | | OFED 4.6 |
1628 | | | rdma-core 24 | | rdma-core 23 |
1629 | | | ConnectX-5 | | ConnectX-5 |
1630 +-----------------------+-----------------+-----------------+
1631 | Drop | | DPDK 19.05 | | DPDK 18.11 |
1632 | | | OFED 4.6 | | OFED 4.5 |
1633 | | | rdma-core 24 | | rdma-core 23 |
1634 | | | ConnectX-5 | | ConnectX-4 |
1635 +-----------------------+-----------------+-----------------+
1636 | Queue / RSS | | | | DPDK 18.11 |
1637 | | | N/A | | OFED 4.5 |
1638 | | | | | rdma-core 23 |
1639 | | | | | ConnectX-4 |
1640 +-----------------------+-----------------+-----------------+
1641 | Shared action | | | | |
1642 | | | :numref:`sact`| | :numref:`sact`|
1645 +-----------------------+-----------------+-----------------+
1646 | | VLAN | | DPDK 19.11 | | DPDK 19.11 |
1647 | | (of_pop_vlan / | | OFED 4.7-1 | | OFED 4.7-1 |
1648 | | of_push_vlan / | | ConnectX-5 | | ConnectX-5 |
1649 | | of_set_vlan_pcp / | | | | |
1650 | | of_set_vlan_vid) | | | | |
1651 +-----------------------+-----------------+-----------------+
1652 | | VLAN | | DPDK 21.05 | | |
1653 | | ingress and / | | OFED 5.3 | | N/A |
1654 | | of_push_vlan / | | ConnectX-6 Dx | | |
1655 +-----------------------+-----------------+-----------------+
1656 | | VLAN | | DPDK 21.05 | | |
1657 | | egress and / | | OFED 5.3 | | N/A |
1658 | | of_pop_vlan / | | ConnectX-6 Dx | | |
1659 +-----------------------+-----------------+-----------------+
1660 | Encapsulation | | DPDK 19.05 | | DPDK 19.02 |
1661 | (VXLAN / NVGRE / RAW) | | OFED 4.7-1 | | OFED 4.6 |
1662 | | | rdma-core 24 | | rdma-core 23 |
1663 | | | ConnectX-5 | | ConnectX-5 |
1664 +-----------------------+-----------------+-----------------+
1665 | Encapsulation | | DPDK 19.11 | | DPDK 19.11 |
1666 | GENEVE | | OFED 4.7-3 | | OFED 4.7-3 |
1667 | | | rdma-core 27 | | rdma-core 27 |
1668 | | | ConnectX-5 | | ConnectX-5 |
1669 +-----------------------+-----------------+-----------------+
1670 | Tunnel Offload | | DPDK 20.11 | | DPDK 20.11 |
1671 | | | OFED 5.1-2 | | OFED 5.1-2 |
1672 | | | rdma-core 32 | | N/A |
1673 | | | ConnectX-5 | | ConnectX-5 |
1674 +-----------------------+-----------------+-----------------+
1675 | | Header rewrite | | DPDK 19.05 | | DPDK 19.02 |
1676 | | (set_ipv4_src / | | OFED 4.7-1 | | OFED 4.7-1 |
1677 | | set_ipv4_dst / | | rdma-core 24 | | rdma-core 24 |
1678 | | set_ipv6_src / | | ConnectX-5 | | ConnectX-5 |
1679 | | set_ipv6_dst / | | | | |
1680 | | set_tp_src / | | | | |
1681 | | set_tp_dst / | | | | |
1682 | | dec_ttl / | | | | |
1683 | | set_ttl / | | | | |
1684 | | set_mac_src / | | | | |
1685 | | set_mac_dst) | | | | |
1686 +-----------------------+-----------------+-----------------+
1687 | | Header rewrite | | DPDK 20.02 | | DPDK 20.02 |
1688 | | (set_dscp) | | OFED 5.0 | | OFED 5.0 |
1689 | | | | rdma-core 24 | | rdma-core 24 |
1690 | | | | ConnectX-5 | | ConnectX-5 |
1691 +-----------------------+-----------------+-----------------+
1692 | Jump | | DPDK 19.05 | | DPDK 19.02 |
1693 | | | OFED 4.7-1 | | OFED 4.7-1 |
1694 | | | rdma-core 24 | | N/A |
1695 | | | ConnectX-5 | | ConnectX-5 |
1696 +-----------------------+-----------------+-----------------+
1697 | Mark / Flag | | DPDK 19.05 | | DPDK 18.11 |
1698 | | | OFED 4.6 | | OFED 4.5 |
1699 | | | rdma-core 24 | | rdma-core 23 |
1700 | | | ConnectX-5 | | ConnectX-4 |
1701 +-----------------------+-----------------+-----------------+
1702 | Meta data | | DPDK 19.11 | | DPDK 19.11 |
1703 | | | OFED 4.7-3 | | OFED 4.7-3 |
1704 | | | rdma-core 26 | | rdma-core 26 |
1705 | | | ConnectX-5 | | ConnectX-5 |
1706 +-----------------------+-----------------+-----------------+
1707 | Port ID | | DPDK 19.05 | | N/A |
1708 | | | OFED 4.7-1 | | N/A |
1709 | | | rdma-core 24 | | N/A |
1710 | | | ConnectX-5 | | N/A |
1711 +-----------------------+-----------------+-----------------+
1712 | Hairpin | | | | DPDK 19.11 |
1713 | | | N/A | | OFED 4.7-3 |
1714 | | | | | rdma-core 26 |
1715 | | | | | ConnectX-5 |
1716 +-----------------------+-----------------+-----------------+
1717 | 2-port Hairpin | | | | DPDK 20.11 |
1718 | | | N/A | | OFED 5.1-2 |
1720 | | | | | ConnectX-5 |
1721 +-----------------------+-----------------+-----------------+
1722 | Metering | | DPDK 19.11 | | DPDK 19.11 |
1723 | | | OFED 4.7-3 | | OFED 4.7-3 |
1724 | | | rdma-core 26 | | rdma-core 26 |
1725 | | | ConnectX-5 | | ConnectX-5 |
1726 +-----------------------+-----------------+-----------------+
1727 | Sampling | | DPDK 20.11 | | DPDK 20.11 |
1728 | | | OFED 5.1-2 | | OFED 5.1-2 |
1729 | | | rdma-core 32 | | N/A |
1730 | | | ConnectX-5 | | ConnectX-5 |
1731 +-----------------------+-----------------+-----------------+
1732 | Encapsulation | | DPDK 21.02 | | DPDK 21.02 |
1733 | GTP PSC | | OFED 5.2 | | OFED 5.2 |
1734 | | | rdma-core 35 | | rdma-core 35 |
1735 | | | ConnectX-6 Dx| | ConnectX-6 Dx |
1736 +-----------------------+-----------------+-----------------+
1737 | Encapsulation | | DPDK 21.02 | | DPDK 21.02 |
1738 | GENEVE TLV option | | OFED 5.2 | | OFED 5.2 |
1739 | | | rdma-core 34 | | rdma-core 34 |
1740 | | | ConnectX-6 Dx | | ConnectX-6 Dx |
1741 +-----------------------+-----------------+-----------------+
1742 | Modify Field | | DPDK 21.02 | | DPDK 21.02 |
1743 | | | OFED 5.2 | | OFED 5.2 |
1744 | | | rdma-core 35 | | rdma-core 35 |
1745 | | | ConnectX-5 | | ConnectX-5 |
1746 +-----------------------+-----------------+-----------------+
1747 | Connection tracking | | | | DPDK 21.05 |
1748 | | | N/A | | OFED 5.3 |
1749 | | | | | rdma-core 35 |
1750 | | | | | ConnectX-6 Dx |
1751 +-----------------------+-----------------+-----------------+
1753 .. table:: Minimal SW/HW versions for shared action offload
1756 +-----------------------+-----------------+-----------------+
1757 | Shared Action | with E-Switch | with NIC |
1758 +=======================+=================+=================+
1759 | RSS | | | | DPDK 20.11 |
1760 | | | N/A | | OFED 5.2 |
1761 | | | | | rdma-core 33 |
1762 | | | | | ConnectX-5 |
1763 +-----------------------+-----------------+-----------------+
1764 | Age | | DPDK 20.11 | | DPDK 20.11 |
1765 | | | OFED 5.2 | | OFED 5.2 |
1766 | | | rdma-core 32 | | rdma-core 32 |
1767 | | | ConnectX-6 Dx | | ConnectX-6 Dx |
1768 +-----------------------+-----------------+-----------------+
1769 | Count | | DPDK 21.05 | | DPDK 21.05 |
1770 | | | OFED 4.6 | | OFED 4.6 |
1771 | | | rdma-core 24 | | rdma-core 23 |
1772 | | | ConnectX-5 | | ConnectX-5 |
1773 +-----------------------+-----------------+-----------------+
1778 MARK and META items are interrelated with datapath - they might move from/to
1779 the applications in mbuf fields. Hence, zero value for these items has the
1780 special meaning - it means "no metadata are provided", not zero values are
1781 treated by applications and PMD as valid ones.
1783 Moreover in the flow engine domain the value zero is acceptable to match and
1784 set, and we should allow to specify zero values as rte_flow parameters for the
1785 META and MARK items and actions. In the same time zero mask has no meaning and
1786 should be rejected on validation stage.
1791 Flows are not cached in the driver.
1792 When stopping a device port, all the flows created on this port from the
1793 application will be flushed automatically in the background.
1794 After stopping the device port, all flows on this port become invalid and
1795 not represented in the system.
1796 All references to these flows held by the application should be discarded
1797 directly but neither destroyed nor flushed.
1799 The application should re-create the flows as required after the port restart.
1804 Compared to librte_net_mlx4 that implements a single RSS configuration per
1805 port, librte_net_mlx5 supports per-protocol RSS configuration.
1807 Since ``testpmd`` defaults to IP RSS mode and there is currently no
1808 command-line parameter to enable additional protocols (UDP and TCP as well
1809 as IP), the following commands must be entered from its CLI to get the same
1810 behavior as librte_net_mlx4::
1813 > port config all rss all
1819 This section demonstrates how to launch **testpmd** with Mellanox
1820 ConnectX-4/ConnectX-5/ConnectX-6/BlueField devices managed by librte_net_mlx5.
1822 #. Load the kernel modules::
1824 modprobe -a ib_uverbs mlx5_core mlx5_ib
1826 Alternatively if MLNX_OFED/MLNX_EN is fully installed, the following script
1829 /etc/init.d/openibd restart
1833 User space I/O kernel modules (uio and igb_uio) are not used and do
1834 not have to be loaded.
1836 #. Make sure Ethernet interfaces are in working order and linked to kernel
1837 verbs. Related sysfs entries should be present::
1839 ls -d /sys/class/net/*/device/infiniband_verbs/uverbs* | cut -d / -f 5
1848 #. Optionally, retrieve their PCI bus addresses for to be used with the allow list::
1851 for intf in eth2 eth3 eth4 eth5;
1853 (cd "/sys/class/net/${intf}/device/" && pwd -P);
1856 sed -n 's,.*/\(.*\),-a \1,p'
1865 #. Request huge pages::
1867 dpdk-hugepages.py --setup 2G
1869 #. Start testpmd with basic parameters::
1871 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
1876 EAL: PCI device 0000:05:00.0 on NUMA socket 0
1877 EAL: probe driver: 15b3:1013 librte_net_mlx5
1878 PMD: librte_net_mlx5: PCI information matches, using device "mlx5_0" (VF: false)
1879 PMD: librte_net_mlx5: 1 port(s) detected
1880 PMD: librte_net_mlx5: port 1 MAC address is e4:1d:2d:e7:0c:fe
1881 EAL: PCI device 0000:05:00.1 on NUMA socket 0
1882 EAL: probe driver: 15b3:1013 librte_net_mlx5
1883 PMD: librte_net_mlx5: PCI information matches, using device "mlx5_1" (VF: false)
1884 PMD: librte_net_mlx5: 1 port(s) detected
1885 PMD: librte_net_mlx5: port 1 MAC address is e4:1d:2d:e7:0c:ff
1886 EAL: PCI device 0000:06:00.0 on NUMA socket 0
1887 EAL: probe driver: 15b3:1013 librte_net_mlx5
1888 PMD: librte_net_mlx5: PCI information matches, using device "mlx5_2" (VF: false)
1889 PMD: librte_net_mlx5: 1 port(s) detected
1890 PMD: librte_net_mlx5: port 1 MAC address is e4:1d:2d:e7:0c:fa
1891 EAL: PCI device 0000:06:00.1 on NUMA socket 0
1892 EAL: probe driver: 15b3:1013 librte_net_mlx5
1893 PMD: librte_net_mlx5: PCI information matches, using device "mlx5_3" (VF: false)
1894 PMD: librte_net_mlx5: 1 port(s) detected
1895 PMD: librte_net_mlx5: port 1 MAC address is e4:1d:2d:e7:0c:fb
1896 Interactive-mode selected
1897 Configuring Port 0 (socket 0)
1898 PMD: librte_net_mlx5: 0x8cba80: TX queues number update: 0 -> 2
1899 PMD: librte_net_mlx5: 0x8cba80: RX queues number update: 0 -> 2
1900 Port 0: E4:1D:2D:E7:0C:FE
1901 Configuring Port 1 (socket 0)
1902 PMD: librte_net_mlx5: 0x8ccac8: TX queues number update: 0 -> 2
1903 PMD: librte_net_mlx5: 0x8ccac8: RX queues number update: 0 -> 2
1904 Port 1: E4:1D:2D:E7:0C:FF
1905 Configuring Port 2 (socket 0)
1906 PMD: librte_net_mlx5: 0x8cdb10: TX queues number update: 0 -> 2
1907 PMD: librte_net_mlx5: 0x8cdb10: RX queues number update: 0 -> 2
1908 Port 2: E4:1D:2D:E7:0C:FA
1909 Configuring Port 3 (socket 0)
1910 PMD: librte_net_mlx5: 0x8ceb58: TX queues number update: 0 -> 2
1911 PMD: librte_net_mlx5: 0x8ceb58: RX queues number update: 0 -> 2
1912 Port 3: E4:1D:2D:E7:0C:FB
1913 Checking link statuses...
1914 Port 0 Link Up - speed 40000 Mbps - full-duplex
1915 Port 1 Link Up - speed 40000 Mbps - full-duplex
1916 Port 2 Link Up - speed 10000 Mbps - full-duplex
1917 Port 3 Link Up - speed 10000 Mbps - full-duplex
1924 This section demonstrates how to dump flows. Currently, it's possible to dump
1925 all flows with assistance of external tools.
1927 #. 2 ways to get flow raw file:
1929 - Using testpmd CLI:
1931 .. code-block:: console
1934 testpmd> flow dump <port> all <output_file>
1936 testpmd> flow dump <port> rule <rule_id> <output_file>
1938 - call rte_flow_dev_dump api:
1940 .. code-block:: console
1942 rte_flow_dev_dump(port, flow, file, NULL);
1944 #. Dump human-readable flows from raw file:
1946 Get flow parsing tool from: https://github.com/Mellanox/mlx_steering_dump
1948 .. code-block:: console
1950 mlx_steering_dump.py -f <output_file> -flowptr <flow_ptr>
1952 How to share a meter between ports in the same switch domain
1953 ------------------------------------------------------------
1955 This section demonstrates how to use the shared meter. A meter M can be created
1956 on port X and to be shared with a port Y on the same switch domain by the next way:
1958 .. code-block:: console
1960 flow create X ingress transfer pattern eth / port_id id is Y / end actions meter mtr_id M / end
1962 How to use meter hierarchy
1963 --------------------------
1965 This section demonstrates how to create and use a meter hierarchy.
1966 A termination meter M can be the policy green action of another termination meter N.
1967 The two meters are chained together as a chain. Using meter N in a flow will apply
1968 both the meters in hierarchy on that flow.
1970 .. code-block:: console
1972 add port meter policy 0 1 g_actions queue index 0 / end y_actions end r_actions drop / end
1973 create port meter 0 M 1 1 yes 0xffff 1 0
1974 add port meter policy 0 2 g_actions meter mtr_id M / end y_actions end r_actions drop / end
1975 create port meter 0 N 2 2 yes 0xffff 1 0
1976 flow create 0 ingress group 1 pattern eth / end actions meter mtr_id N / end