2022-07-09 08:43:09 +00:00
|
|
|
.. SPDX-License-Identifier: BSD-3-Clause
|
|
|
|
|
Copyright 2022 The DPDK contributors
|
|
|
|
|
|
|
|
|
|
.. include:: <isonum.txt>
|
|
|
|
|
|
|
|
|
|
DPDK Release 22.11
|
|
|
|
|
==================
|
|
|
|
|
|
|
|
|
|
New Features
|
|
|
|
|
------------
|
|
|
|
|
|
2022-10-04 15:40:42 +00:00
|
|
|
* **Added initial LoongArch architecture support.**
|
|
|
|
|
|
|
|
|
|
Added EAL implementation for LoongArch architecture.
|
2022-11-24 16:56:10 +00:00
|
|
|
The initial port was tested on Loongson 3A5000,
|
2022-10-04 15:40:42 +00:00
|
|
|
Loongson 3C5000 and Loongson 3C5000L.
|
|
|
|
|
In theory this implementation should work with any target based on
|
|
|
|
|
``LoongArch`` ISA.
|
|
|
|
|
|
2022-10-07 17:29:19 +00:00
|
|
|
* **Added support for multiple mbuf pools per ethdev Rx queue.**
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
Added a capability which allows an application to provide many mempools
|
|
|
|
|
of different size, and PMDs and/or NICs to choose a memory pool
|
|
|
|
|
based on the packet's length and/or Rx buffer availability.
|
2022-10-07 17:29:19 +00:00
|
|
|
|
2022-10-04 09:02:57 +00:00
|
|
|
* **Added support for congestion management in ethdev.**
|
|
|
|
|
|
|
|
|
|
Added new API functions ``rte_eth_cman_config_init()``,
|
2022-11-24 16:56:10 +00:00
|
|
|
``rte_eth_cman_config_get()``, ``rte_eth_cman_config_set()``
|
|
|
|
|
and ``rte_eth_cman_info_get()`` to support congestion management.
|
2022-10-04 09:02:57 +00:00
|
|
|
|
2022-10-09 20:25:38 +00:00
|
|
|
* **Added protocol header based buffer split.**
|
|
|
|
|
|
|
|
|
|
* Added ``rte_eth_buffer_split_get_supported_hdr_ptypes()`` to get supported
|
|
|
|
|
header protocols to split at.
|
2022-11-24 16:56:10 +00:00
|
|
|
* Added support for protocol-based buffer split using new ``proto_hdr``
|
|
|
|
|
field in structure ``rte_eth_rxseg_split``.
|
2022-10-09 20:25:38 +00:00
|
|
|
|
ethdev: add proactive error handling mode
Some PMDs (e.g. hns3) could detect hardware or firmware errors, one
error recovery mode is to report RTE_ETH_EVENT_INTR_RESET event, and
wait for application invoke rte_eth_dev_reset() to recover the port,
however, this mode has the following weaknesses:
1) Due to different hardware and software design, some NIC port recovery
process requires multiple handshakes with the firmware and PF (when the
port is VF). It takes a long time to complete the entire operation for
one port, If multiple ports (for example, multiple VFs of a PF) are
reset at the same time, other VFs may fail to be reset. (Because the
reset processing is serial, the previous VFs must be processed before
the subsequent VFs).
2) The impact on the application layer is great, and it should stop
working queues, stop calling Rx and Tx functions, and then call
rte_eth_dev_reset(), and re-setup all again.
This patch introduces proactive error handling mode, the PMD will try
to recover from the errors itself. In this process, the PMD sets the
data path pointers to dummy functions (which will prevent the crash),
and also make sure the control path operations failed with retcode
-EBUSY.
Because the PMD recovers automatically, the application can only sense
that the data flow is disconnected for a while and the control API
returns an error in this period.
In order to sense the error happening/recovering, three events were
introduced:
1) RTE_ETH_EVENT_ERR_RECOVERING: used to notify the application that it
detected an error and the recovery is being started. Upon receiving the
event, the application should not invoke any control path APIs until
receiving RTE_ETH_EVENT_RECOVERY_SUCCESS or
RTE_ETH_EVENT_RECOVERY_FAILED event.
2) RTE_ETH_EVENT_RECOVERY_SUCCESS: used to notify the application that
it recovers successful from the error, the PMD already re-configures the
port, and the effect is the same as that of the restart operation.
3) RTE_ETH_EVENT_RECOVERY_FAILED: used to notify the application that it
recovers failed from the error, the port should not usable anymore. The
application should close the port.
Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com>
Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2022-10-13 12:42:24 +00:00
|
|
|
* **Added proactive error handling mode for ethdev.**
|
|
|
|
|
|
|
|
|
|
Added proactive error handling mode for ethdev,
|
2022-11-24 16:56:10 +00:00
|
|
|
and introduced three new events: ``RTE_ETH_EVENT_ERR_RECOVERING``
|
ethdev: add proactive error handling mode
Some PMDs (e.g. hns3) could detect hardware or firmware errors, one
error recovery mode is to report RTE_ETH_EVENT_INTR_RESET event, and
wait for application invoke rte_eth_dev_reset() to recover the port,
however, this mode has the following weaknesses:
1) Due to different hardware and software design, some NIC port recovery
process requires multiple handshakes with the firmware and PF (when the
port is VF). It takes a long time to complete the entire operation for
one port, If multiple ports (for example, multiple VFs of a PF) are
reset at the same time, other VFs may fail to be reset. (Because the
reset processing is serial, the previous VFs must be processed before
the subsequent VFs).
2) The impact on the application layer is great, and it should stop
working queues, stop calling Rx and Tx functions, and then call
rte_eth_dev_reset(), and re-setup all again.
This patch introduces proactive error handling mode, the PMD will try
to recover from the errors itself. In this process, the PMD sets the
data path pointers to dummy functions (which will prevent the crash),
and also make sure the control path operations failed with retcode
-EBUSY.
Because the PMD recovers automatically, the application can only sense
that the data flow is disconnected for a while and the control API
returns an error in this period.
In order to sense the error happening/recovering, three events were
introduced:
1) RTE_ETH_EVENT_ERR_RECOVERING: used to notify the application that it
detected an error and the recovery is being started. Upon receiving the
event, the application should not invoke any control path APIs until
receiving RTE_ETH_EVENT_RECOVERY_SUCCESS or
RTE_ETH_EVENT_RECOVERY_FAILED event.
2) RTE_ETH_EVENT_RECOVERY_SUCCESS: used to notify the application that
it recovers successful from the error, the PMD already re-configures the
port, and the effect is the same as that of the restart operation.
3) RTE_ETH_EVENT_RECOVERY_FAILED: used to notify the application that it
recovers failed from the error, the port should not usable anymore. The
application should close the port.
Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com>
Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2022-10-13 12:42:24 +00:00
|
|
|
to report that the port is recovering from an error,
|
|
|
|
|
``RTE_ETH_EVENT_RECOVER_SUCCESS`` and ``RTE_ETH_EVENT_RECOVER_FAILED``.
|
|
|
|
|
|
2022-10-06 12:05:12 +00:00
|
|
|
* **Added ethdev Rx/Tx descriptor dump API.**
|
|
|
|
|
|
|
|
|
|
Added the ethdev Rx/Tx descriptor dump API which provides functions
|
|
|
|
|
for querying descriptor from device.
|
|
|
|
|
The descriptor information differs in different NICs.
|
|
|
|
|
The information demonstrates I/O process which is important for debug.
|
|
|
|
|
The dump format is vendor-specific.
|
|
|
|
|
|
ethdev: introduce hairpin memory capabilities
Before this patch, implementation details and configuration of hairpin
queues were decided internally by the PMD. Applications had no control
over the configuration of Rx and Tx hairpin queues, despite number of
descriptors, explicit Tx flow mode and disabling automatic binding.
This patch addresses that by adding:
- Hairpin queue capabilities reported by PMDs.
- New configuration options for Rx and Tx hairpin queues.
Main goal of this patch is to allow applications to provide
configuration hints regarding placement of hairpin queues.
These hints specify whether buffers of hairpin queues should be placed
in host memory or in dedicated device memory. Different memory options
may have different performance characteristics and hairpin configuration
should be fine-tuned to the specific application and use case.
This patch introduces new hairpin queue configuration options through
rte_eth_hairpin_conf struct, allowing to tune Rx and Tx hairpin queues
memory configuration. Hairpin configuration is extended with the
following fields:
- use_locked_device_memory - If set, PMD will use specialized on-device
memory to store RX or TX hairpin queue data.
- use_rte_memory - If set, PMD will use DPDK-managed memory to store RX
or TX hairpin queue data.
- force_memory - If set, PMD will be forced to use provided memory
settings. If no appropriate resources are available, then device start
will fail. If unset and no resources are available, PMD will fallback
to using default type of resource for given queue.
If application chooses to use PMD default memory configuration, all of
these flags should remain unset.
Hairpin capabilities are also extended, to allow verification of support
of given hairpin memory configurations. Struct rte_eth_hairpin_cap is
extended with two additional fields of type rte_eth_hairpin_queue_cap:
- rx_cap - memory capabilities of hairpin RX queues.
- tx_cap - memory capabilities of hairpin TX queues.
Struct rte_eth_hairpin_queue_cap exposes whether given queue type
supports use_locked_device_memory and use_rte_memory flags.
Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
2022-10-06 11:00:58 +00:00
|
|
|
* **Added ethdev hairpin memory configuration options.**
|
|
|
|
|
|
|
|
|
|
Added new configuration flags for hairpin queues in ``rte_eth_hairpin_conf``:
|
|
|
|
|
|
|
|
|
|
* ``use_locked_device_memory``
|
|
|
|
|
* ``use_rte_memory``
|
|
|
|
|
* ``force_memory``
|
|
|
|
|
|
|
|
|
|
Each flag has a corresponding capability flag
|
|
|
|
|
in ``struct rte_eth_hairpin_queue_cap``.
|
|
|
|
|
|
2022-11-16 12:56:28 +00:00
|
|
|
* **Added strict queue to pre-configuration flow hints.**
|
|
|
|
|
|
|
|
|
|
* Added flags option to ``rte_flow_configure`` and ``rte_flow_info_get``.
|
|
|
|
|
* Added ``RTE_FLOW_PORT_FLAG_STRICT_QUEUE`` flag to indicate all operations
|
|
|
|
|
for a given flow rule will strictly happen on the same flow queue.
|
|
|
|
|
|
2022-09-20 07:10:36 +00:00
|
|
|
* **Added configuration for asynchronous flow connection tracking.**
|
|
|
|
|
|
|
|
|
|
Added connection tracking action number hint to ``rte_flow_configure``
|
|
|
|
|
and ``rte_flow_info_get``.
|
2022-11-24 16:56:10 +00:00
|
|
|
The PMD can prepare the connection tracking resources according to the hint.
|
2022-09-20 07:10:36 +00:00
|
|
|
|
2022-09-20 07:11:41 +00:00
|
|
|
* **Added support for queue-based async query in flow API.**
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
Added new function ``rte_flow_async_action_handle_query()``
|
2022-09-20 07:11:41 +00:00
|
|
|
to query the action asynchronously.
|
|
|
|
|
|
2022-09-26 14:57:39 +00:00
|
|
|
* **Extended metering and marking support in the flow API.**
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
* Added ``METER_COLOR`` item to match color marker set by a meter.
|
2022-09-26 14:57:40 +00:00
|
|
|
* Added ability to set color marker via modify field flow API.
|
2022-11-24 16:56:10 +00:00
|
|
|
* Added meter API to get a pointer to the profile/policy by their ID.
|
|
|
|
|
* Added ``METER_MARK`` action for metering with lockless profile/policy access.
|
2022-09-26 14:57:39 +00:00
|
|
|
|
2022-10-03 16:34:49 +00:00
|
|
|
* **Added flow offload action to route packets to kernel.**
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
Added new flow action which allows an application to re-route packets
|
2022-10-03 16:34:49 +00:00
|
|
|
directly to the kernel without software involvement.
|
|
|
|
|
|
2022-10-06 06:26:54 +00:00
|
|
|
* **Updated AF_XDP driver.**
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
* Updated AF_XDP driver to make it compatible with libbpf v0.8.0
|
|
|
|
|
(when used with libxdp).
|
2022-10-06 06:26:54 +00:00
|
|
|
|
2022-10-18 19:41:01 +00:00
|
|
|
* **Updated AMD Pensando ionic driver.**
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
* Updated ionic driver to reflect that Pensando has been acquired by AMD.
|
2022-10-18 19:41:15 +00:00
|
|
|
* Enhanced data path to provide substantial performance improvements.
|
2022-10-18 19:41:17 +00:00
|
|
|
* Added support for mbuf fast free.
|
2022-10-18 19:41:21 +00:00
|
|
|
* Added support for advertising packet types.
|
2022-10-18 19:41:22 +00:00
|
|
|
* Added support for descriptor status functions.
|
2022-10-18 19:41:24 +00:00
|
|
|
* Added Q-in-CMB feature controlled by device option ``ionic_cmb``.
|
2022-10-18 19:41:28 +00:00
|
|
|
* Added optimized handlers for non-scattered Rx and Tx.
|
2022-10-18 19:41:01 +00:00
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
* **Added GVE net PMD.**
|
2022-10-25 09:07:24 +00:00
|
|
|
|
|
|
|
|
* Added the new ``gve`` net driver for Google Virtual Ethernet devices.
|
|
|
|
|
* See the :doc:`../nics/gve` NIC guide for more details on this new driver.
|
|
|
|
|
|
2022-09-07 05:10:37 +00:00
|
|
|
* **Updated Intel iavf driver.**
|
|
|
|
|
|
|
|
|
|
* Added flow subscription support.
|
|
|
|
|
|
2022-10-09 20:25:41 +00:00
|
|
|
* **Updated Intel ice driver.**
|
|
|
|
|
|
|
|
|
|
* Added protocol based buffer split support in scalar path.
|
|
|
|
|
|
2022-10-31 08:33:30 +00:00
|
|
|
* **Added Intel idpf driver.**
|
|
|
|
|
|
|
|
|
|
Added the new ``idpf`` net driver
|
2022-11-01 06:12:50 +00:00
|
|
|
for Intel\ |reg| Infrastructure Processing Unit (Intel\ |reg| IPU) E2100.
|
2022-10-31 08:33:30 +00:00
|
|
|
See the :doc:`../nics/idpf` NIC guide for more details on this new driver.
|
|
|
|
|
|
2022-08-12 19:18:19 +00:00
|
|
|
* **Updated Marvell cnxk driver.**
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
* Added support for flow action ``REPRESENTED_PORT``.
|
2022-09-29 09:54:54 +00:00
|
|
|
* Added support for congestion management.
|
2022-08-12 19:18:19 +00:00
|
|
|
|
2022-10-05 23:21:51 +00:00
|
|
|
* **Added Microsoft mana driver.**
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
The driver has been disabled by default because of a, currently, missing dependency.
|
2022-10-13 11:47:53 +00:00
|
|
|
|
2022-09-26 06:59:48 +00:00
|
|
|
* **Updated Netronome nfp driver.**
|
|
|
|
|
|
2022-10-21 08:01:43 +00:00
|
|
|
Added flow API support:
|
2022-09-26 06:59:48 +00:00
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
* Added support for the flower firmware.
|
2022-09-26 06:59:48 +00:00
|
|
|
* Added the flower service infrastructure.
|
2022-09-26 06:59:52 +00:00
|
|
|
* Added the control message interactive channels between PMD and firmware.
|
2022-11-24 16:56:10 +00:00
|
|
|
* Added support for a representor port.
|
2022-09-26 06:59:48 +00:00
|
|
|
|
2022-10-20 15:57:48 +00:00
|
|
|
* **Updated NVIDIA mlx5 driver.**
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
* Added full support for queue-based async hardware steering.
|
2022-11-16 12:56:26 +00:00
|
|
|
|
2022-10-20 15:41:40 +00:00
|
|
|
- Support of FDB.
|
2022-10-20 15:41:52 +00:00
|
|
|
- Support of control flow and isolate mode.
|
2022-10-20 15:41:44 +00:00
|
|
|
- Support of conntrack.
|
net/mlx5: support flow counter action for HWS
This commit adds HW steering counter action support.
The pool mechanism is the basic data structure for the HW steering
counter.
The HW steering's counter pool is based on the rte_ring of zero-copy
variation.
There are two global rte_rings:
1. free_list:
Store the counters indexes, which are ready for use.
2. wait_reset_list:
Store the counters indexes, which are just freed from the user and
need to query the hardware counter to get the reset value before
this counter can be reused again.
The counter pool also supports cache per HW steering's queues, which are
also based on the rte_ring of zero-copy variation.
The cache can be configured in size, preload, threshold, and fetch size,
they are all exposed via device args.
The main operations of the counter pool are as follows:
- Get one counter from the pool:
1. The user call _get_* API.
2. If the cache is enabled, dequeue one counter index from the local
cache:
2. A: if the dequeued one from the local cache is still in reset
status (counter's query_gen_when_free is equal to pool's query
gen):
I. Flush all counters in the local cache back to global
wait_reset_list.
II. Fetch _fetch_sz_ counters into the cache from the global
free list.
III. Fetch one counter from the cache.
3. If the cache is empty, fetch _fetch_sz_ counters from the global
free list into the cache and fetch one counter from the cache.
- Free one counter into the pool:
1. The user calls _put_* API.
2. Put the counter into the local cache.
3. If the local cache is full:
A: Write back all counters above _threshold_ into the global
wait_reset_list.
B: Also, write back this counter into the global wait_reset_list.
When the local cache is disabled, _get_/_put_ cache directly from/into
global list.
Signed-off-by: Xiaoyu Min <jackmin@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
2022-10-20 15:41:42 +00:00
|
|
|
- Support of counter.
|
2022-11-16 12:56:27 +00:00
|
|
|
- Support of aging.
|
2022-10-20 15:41:41 +00:00
|
|
|
- Support of meter.
|
2022-10-20 15:41:38 +00:00
|
|
|
- Support of modify fields.
|
2022-10-20 15:57:48 +00:00
|
|
|
|
2022-08-12 19:18:18 +00:00
|
|
|
* **Updated NXP dpaa2 driver.**
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
* Added support for flow action ``REPRESENTED_PORT``.
|
2022-08-12 19:18:18 +00:00
|
|
|
|
2022-09-02 03:00:11 +00:00
|
|
|
* **Updated Wangxun ngbe driver.**
|
|
|
|
|
|
|
|
|
|
* Added support to set device link down/up.
|
|
|
|
|
|
2022-10-25 08:25:39 +00:00
|
|
|
* **Added DMA vChannel unconfiguration for async vhost.**
|
|
|
|
|
|
|
|
|
|
Added support to unconfigure DMA vChannel that is no longer used
|
|
|
|
|
by the vhost library.
|
|
|
|
|
|
2022-10-17 07:48:17 +00:00
|
|
|
* **Added non-blocking notify API to vhost library.**
|
|
|
|
|
|
|
|
|
|
Added ``rte_vhost_vring_call_nonblock`` API to notify the guest that
|
2022-11-24 16:56:10 +00:00
|
|
|
used descriptors have been added to the vring in n aon-blocking way.
|
|
|
|
|
The user should check the return value of this API and try again if needed.
|
2022-10-17 07:48:17 +00:00
|
|
|
|
2022-09-28 12:22:53 +00:00
|
|
|
* **Added support for MACsec in rte_security.**
|
|
|
|
|
|
|
|
|
|
Added MACsec transform for rte_security session and added new API
|
|
|
|
|
to configure security associations (SA) and secure channels (SC).
|
|
|
|
|
|
2022-09-28 13:18:00 +00:00
|
|
|
* **Added new algorithms to cryptodev.**
|
|
|
|
|
|
2022-09-28 13:18:01 +00:00
|
|
|
* Added symmetric hash algorithm ShangMi 3 (SM3).
|
2022-09-28 13:18:00 +00:00
|
|
|
* Added symmetric cipher algorithm ShangMi 4 (SM4) in ECB, CBC and CTR modes.
|
|
|
|
|
|
2022-10-20 15:09:39 +00:00
|
|
|
* **Updated Intel QuickAssist Technology (QAT) crypto driver.**
|
2022-09-30 09:41:07 +00:00
|
|
|
|
2022-09-30 09:41:08 +00:00
|
|
|
* Added support for SM3 hash algorithm.
|
2022-09-30 09:41:07 +00:00
|
|
|
* Added support for SM4 encryption algorithm in ECB, CBC and CTR modes.
|
2022-10-20 15:09:39 +00:00
|
|
|
* Added support for ECDH key exchange algorithm.
|
2022-09-30 09:41:07 +00:00
|
|
|
|
2022-08-09 10:53:39 +00:00
|
|
|
* **Updated Marvell cnxk crypto driver.**
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
* Added AES-CCM support in lookaside protocol (IPsec) for CN9K and CN10K.
|
2022-08-09 10:53:56 +00:00
|
|
|
* Added AES & DES DOCSIS algorithm support in lookaside crypto for CN9K.
|
2022-08-09 10:53:39 +00:00
|
|
|
|
2022-08-24 15:58:26 +00:00
|
|
|
* **Updated aesni_mb crypto driver.**
|
|
|
|
|
|
|
|
|
|
* Added support for 8-byte and 16-byte tags for ZUC-EIA3-256.
|
2022-10-07 13:46:51 +00:00
|
|
|
* Added support for in-place SGL, out-of-place SGL in SGL out,
|
|
|
|
|
out-of-place LB in SGL out, and out-of-place SGL in LB out.
|
2022-08-24 15:58:26 +00:00
|
|
|
|
2022-11-07 08:49:37 +00:00
|
|
|
* **Updated ipsec_mb crypto driver.**
|
|
|
|
|
|
2022-11-21 16:35:17 +00:00
|
|
|
* Added SNOW-3G and ZUC support for ARM platform.
|
|
|
|
|
* Added Intel IPsec MB v1.3 library support for x86 platform.
|
2022-11-07 08:49:37 +00:00
|
|
|
|
2022-10-27 03:25:05 +00:00
|
|
|
* **Added UADK crypto driver.**
|
|
|
|
|
|
|
|
|
|
Added a new crypto driver for the UADK library. See the
|
|
|
|
|
:doc:`../cryptodevs/uadk` guide for more details on this new driver.
|
|
|
|
|
|
2022-10-04 17:16:54 +00:00
|
|
|
* **Added bbdev operation for FFT processing.**
|
|
|
|
|
|
|
|
|
|
Added a new operation type in bbdev for FFT processing with new functions
|
2022-11-24 16:56:10 +00:00
|
|
|
``rte_bbdev_enqueue_fft_ops`` and ``rte_bbdev_dequeue_fft_ops``,
|
2022-10-04 17:16:54 +00:00
|
|
|
and related structures.
|
|
|
|
|
|
2022-10-12 17:59:18 +00:00
|
|
|
* **Added Intel ACC200 bbdev driver.**
|
|
|
|
|
|
|
|
|
|
Added a new ``acc200`` bbdev driver for the Intel\ |reg| ACC200 accelerator
|
|
|
|
|
integrated on SPR-EE. See the
|
|
|
|
|
:doc:`../bbdevs/acc200` guide for more details on this new driver.
|
|
|
|
|
|
2022-08-29 08:14:31 +00:00
|
|
|
* **Added eventdev adapter instance get API.**
|
|
|
|
|
|
|
|
|
|
* Added ``rte_event_eth_rx_adapter_instance_get`` to get Rx adapter
|
|
|
|
|
instance ID for specified ethernet device ID and Rx queue index.
|
|
|
|
|
|
2022-08-29 08:14:34 +00:00
|
|
|
* Added ``rte_event_eth_tx_adapter_instance_get`` to get Tx adapter
|
|
|
|
|
instance ID for specified ethernet device ID and Tx queue index.
|
|
|
|
|
|
2022-09-26 02:04:12 +00:00
|
|
|
* **Added eventdev Tx adapter queue start/stop API.**
|
|
|
|
|
|
|
|
|
|
* Added ``rte_event_eth_tx_adapter_queue_start`` to start
|
|
|
|
|
enqueueing packets to the Tx queue by Tx adapter.
|
|
|
|
|
* Added ``rte_event_eth_tx_adapter_queue_stop`` to stop the Tx Adapter
|
|
|
|
|
from enqueueing any packets to the Tx queue.
|
|
|
|
|
|
2022-10-01 00:42:12 +00:00
|
|
|
* **Added event crypto adapter vectorization support.**
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
Added support for aggregating crypto operations processed by event crypto adapter
|
|
|
|
|
into a single event containing ``rte_event_vector``
|
2022-10-01 00:42:12 +00:00
|
|
|
whose event type is ``RTE_EVENT_TYPE_CRYPTODEV_VECTOR``.
|
member: add NitroSketch mode
Sketching algorithm provide high-fidelity approximate measurements and
appears as a promising alternative to traditional approaches such as
packet sampling.
NitroSketch [1] is a software sketching framework that optimizes
performance, provides accuracy guarantees, and supports a variety of
sketches.
This commit adds a new data structure called sketch into
membership library. This new data structure is an efficient
way to profile the traffic for heavy hitters. Also use min-heap
structure to maintain the top-k flow keys.
[1] Zaoxing Liu, Ran Ben-Basat, Gil Einziger, Yaron Kassner, Vladimir
Braverman, Roy Friedman, Vyas Sekar, "NitroSketch: Robust and General
Sketch-based Monitoring in Software Switches", in ACM SIGCOMM 2019.
https://dl.acm.org/doi/pdf/10.1145/3341302.3342076
Signed-off-by: Alan Liu <zaoxingliu@gmail.com>
Signed-off-by: Yipeng Wang <yipeng1.wang@intel.com>
Signed-off-by: Leyi Rong <leyi.rong@intel.com>
Tested-by: Yu Jiang <yux.jiang@intel.com>
2022-09-16 03:03:16 +00:00
|
|
|
|
|
|
|
|
* **Added NitroSketch in membership library.**
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
Added a new data structure called sketch into the membership library,
|
member: add NitroSketch mode
Sketching algorithm provide high-fidelity approximate measurements and
appears as a promising alternative to traditional approaches such as
packet sampling.
NitroSketch [1] is a software sketching framework that optimizes
performance, provides accuracy guarantees, and supports a variety of
sketches.
This commit adds a new data structure called sketch into
membership library. This new data structure is an efficient
way to profile the traffic for heavy hitters. Also use min-heap
structure to maintain the top-k flow keys.
[1] Zaoxing Liu, Ran Ben-Basat, Gil Einziger, Yaron Kassner, Vladimir
Braverman, Roy Friedman, Vyas Sekar, "NitroSketch: Robust and General
Sketch-based Monitoring in Software Switches", in ACM SIGCOMM 2019.
https://dl.acm.org/doi/pdf/10.1145/3341302.3342076
Signed-off-by: Alan Liu <zaoxingliu@gmail.com>
Signed-off-by: Yipeng Wang <yipeng1.wang@intel.com>
Signed-off-by: Leyi Rong <leyi.rong@intel.com>
Tested-by: Yu Jiang <yux.jiang@intel.com>
2022-09-16 03:03:16 +00:00
|
|
|
to profile the traffic efficiently.
|
|
|
|
|
NitroSketch provides high-fidelity approximate measurements
|
|
|
|
|
and appears as a promising alternative to traditional approaches
|
|
|
|
|
such as packet sampling.
|
2022-10-06 09:38:01 +00:00
|
|
|
|
|
|
|
|
* **Added Intel uncore frequency control API to the power library.**
|
|
|
|
|
|
|
|
|
|
Added API to allow uncore frequency adjustment.
|
|
|
|
|
This is done through manipulating related uncore frequency control
|
|
|
|
|
sysfs entries to adjust the minimum and maximum uncore frequency values,
|
|
|
|
|
which works on Linux with Intel hardware only.
|
2022-10-01 00:42:12 +00:00
|
|
|
|
2022-11-03 12:46:11 +00:00
|
|
|
* **Added security performance test application.**
|
|
|
|
|
|
|
|
|
|
Added new application to test ``rte_security`` session create/destroy
|
|
|
|
|
performance.
|
|
|
|
|
See the :doc:`../tools/securityperf` for more details.
|
|
|
|
|
|
2022-10-10 16:56:26 +00:00
|
|
|
* **Updated IPsec sample application.**
|
|
|
|
|
|
|
|
|
|
Added support for lookaside sessions in event mode.
|
|
|
|
|
See the :doc:`../sample_app_ug/ipsec_secgw` for more details.
|
|
|
|
|
|
2022-10-12 06:12:36 +00:00
|
|
|
* **Updated FIPS validation sample application.**
|
|
|
|
|
|
|
|
|
|
Added support for asymmetric crypto algorithms.
|
|
|
|
|
See the :doc:`../sample_app_ug/fips_validation` for more details.
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
* **Rewrote pmdinfo script.**
|
2022-10-04 19:29:09 +00:00
|
|
|
|
|
|
|
|
The ``dpdk-pmdinfo.py`` script was rewritten to produce valid JSON only.
|
|
|
|
|
PCI-IDs parsing has been removed.
|
|
|
|
|
To get a similar output to the (now removed) ``-r/--raw`` flag,
|
|
|
|
|
the following command may be used:
|
|
|
|
|
|
|
|
|
|
.. code-block:: sh
|
|
|
|
|
|
|
|
|
|
strings $dpdk_binary_or_driver | sed -n 's/^PMD_INFO_STRING= //p'
|
|
|
|
|
|
2022-07-09 08:43:09 +00:00
|
|
|
|
|
|
|
|
Removed Items
|
|
|
|
|
-------------
|
|
|
|
|
|
2022-09-27 11:46:25 +00:00
|
|
|
* mem: Removed not implemented and deprecated ``rte_malloc_set_limit``.
|
|
|
|
|
|
2022-08-12 19:18:24 +00:00
|
|
|
* ethdev: removed ``RTE_FLOW_ITEM_TYPE_PF``;
|
2022-11-24 16:56:10 +00:00
|
|
|
use ``RTE_FLOW_ITEM_TYPE_REPRESENTED_PORT`` instead.
|
2022-08-12 19:18:24 +00:00
|
|
|
|
2022-08-12 19:18:25 +00:00
|
|
|
* ethdev: removed ``RTE_FLOW_ITEM_TYPE_VF``;
|
2022-11-24 16:56:10 +00:00
|
|
|
use ``RTE_FLOW_ITEM_TYPE_REPRESENTED_PORT`` instead.
|
2022-08-12 19:18:25 +00:00
|
|
|
|
2022-08-12 19:18:26 +00:00
|
|
|
* ethdev: removed ``RTE_FLOW_ITEM_TYPE_PHY_PORT``;
|
2022-11-24 16:56:10 +00:00
|
|
|
use ``RTE_FLOW_ITEM_TYPE_REPRESENTED_PORT`` instead.
|
2022-08-12 19:18:26 +00:00
|
|
|
|
2022-08-12 19:18:27 +00:00
|
|
|
* ethdev: removed ``RTE_FLOW_ACTION_TYPE_PHY_PORT``;
|
2022-11-24 16:56:10 +00:00
|
|
|
use ``RTE_FLOW_ACTION_TYPE_REPRESENTED_PORT`` instead.
|
2022-08-12 19:18:27 +00:00
|
|
|
|
2022-09-29 09:22:56 +00:00
|
|
|
* ethdev: removed ``OF_SET_MPLS_TTL``, ``OF_DEC_MPLS_TTL``,
|
|
|
|
|
``OF_SET_NW_TTL``, ``OF_COPY_TTL_OUT`` and ``OF_COPY_TTL_IN``
|
|
|
|
|
which are not actually supported by any PMD.
|
2022-09-29 09:22:53 +00:00
|
|
|
``MODIFY_FIELD`` action should be used to do packet edits via flow API.
|
|
|
|
|
|
2022-09-27 11:36:08 +00:00
|
|
|
* vhost: Removed deprecated ``rte_vhost_gpa_to_vva`` and
|
|
|
|
|
``rte_vhost_get_queue_num`` helpers.
|
|
|
|
|
|
2022-07-09 08:43:09 +00:00
|
|
|
|
|
|
|
|
API Changes
|
|
|
|
|
-----------
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
* eal: ``RTE_FUNC_PTR_OR_*`` macros have been marked deprecated and will be removed
|
2022-08-23 14:16:43 +00:00
|
|
|
in the future. Applications can use ``devtools/cocci/func_or_ret.cocci``
|
|
|
|
|
to update their code.
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
* eal: Updated ``rte_eal_remote_launch`` so it returns ``-EPIPE`` in case of
|
2022-09-29 10:51:01 +00:00
|
|
|
a read or write error on the pipe, instead of calling ``rte_panic``.
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
* eal: Updated return types for ``rte_{bsf,fls}`` inline functions
|
2022-08-08 21:21:30 +00:00
|
|
|
to be consistently ``uint32_t``.
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
* mempool: Deprecated helper macro ``MEMPOOL_HEADER_SIZE()`` has been removed.
|
2022-07-28 09:35:56 +00:00
|
|
|
The replacement macro ``RTE_MEMPOOL_HEADER_SIZE()`` is internal only.
|
|
|
|
|
|
2022-07-28 09:35:57 +00:00
|
|
|
* mempool: Deprecated macro to register mempool driver
|
2022-11-24 16:56:10 +00:00
|
|
|
``MEMPOOL_REGISTER_OPS()`` has been removed. Use replacement macro
|
2022-07-28 09:35:57 +00:00
|
|
|
``RTE_MEMPOOL_REGISTER_OPS()`` instead.
|
|
|
|
|
|
2022-07-28 09:35:58 +00:00
|
|
|
* mempool: Deprecated macros ``MEMPOOL_PG_NUM_DEFAULT`` and
|
2022-11-24 16:56:10 +00:00
|
|
|
``MEMPOOL_PG_SHIFT_MAX`` have been removed. These macros are not used and
|
2022-07-28 09:35:58 +00:00
|
|
|
not required any more.
|
|
|
|
|
|
2022-08-05 08:02:42 +00:00
|
|
|
* mbuf: Removed deprecated ``PKT_*`` flags.
|
|
|
|
|
Use corresponding flags with ``RTE_MBUF_F_`` prefix instead.
|
2022-11-24 16:56:10 +00:00
|
|
|
Applications can use ``devtools/cocci/prefix_mbuf_offload_flags.cocci``
|
2022-08-05 08:02:42 +00:00
|
|
|
to replace all occurrences of old mbuf flags in C code.
|
|
|
|
|
|
2022-10-04 14:58:50 +00:00
|
|
|
* bus: Changed the device numa node to -1 when NUMA information is unavailable.
|
|
|
|
|
The ``dev->device.numa_node`` field is set by each bus driver for
|
|
|
|
|
every device it manages to indicate on which NUMA node this device lies.
|
|
|
|
|
When this information is unknown, the assigned value was not consistent
|
|
|
|
|
across the bus drivers. This similarly impacts ``rte_eth_dev_socket_id()``.
|
|
|
|
|
|
2022-07-28 15:26:35 +00:00
|
|
|
* bus: Registering a bus has been marked as an internal API.
|
|
|
|
|
External users may still register their bus using the ``bus_driver.h``
|
|
|
|
|
driver header (see ``enable_driver_sdk`` meson option).
|
|
|
|
|
The ``rte_bus`` object is now opaque and must be manipulated through added
|
|
|
|
|
accessors.
|
|
|
|
|
|
2022-07-28 15:26:31 +00:00
|
|
|
* drivers: Registering a driver on the ``auxiliary``, ``ifpga``, ``pci``,
|
2022-07-28 15:26:32 +00:00
|
|
|
``vdev``, ``vmbus`` buses has been marked as an internal API.
|
2022-07-28 15:26:25 +00:00
|
|
|
External users may still register their driver using the associated driver
|
|
|
|
|
headers (see ``enable_driver_sdk`` meson option).
|
2022-07-28 15:26:40 +00:00
|
|
|
The ``rte_driver`` and ``rte_device`` objects are now opaque and must be
|
|
|
|
|
manipulated through added accessors.
|
2022-07-28 15:26:25 +00:00
|
|
|
|
2022-08-04 19:05:53 +00:00
|
|
|
* ethdev: Removed deprecated macros. Applications can use ``devtools/cocci/namespace_ethdev.cocci``
|
|
|
|
|
to update their code.
|
|
|
|
|
|
|
|
|
|
* Removed deprecated ``ETH_LINK_SPEED_*``, ``ETH_SPEED_NUM_*`` and ``ETH_LINK_*``
|
|
|
|
|
(duplex-related) defines. Use corresponding defines with ``RTE_`` prefix
|
|
|
|
|
instead.
|
|
|
|
|
|
2022-08-04 19:05:54 +00:00
|
|
|
* Removed deprecated ``ETH_MQ_RX_*`` and ``ETH_MQ_TX_*`` defines.
|
|
|
|
|
Use corresponding defines with ``RTE_`` prefix instead.
|
|
|
|
|
|
2022-08-04 19:05:55 +00:00
|
|
|
* Removed deprecated ``ETH_RSS_*`` defines for hash function and
|
|
|
|
|
RETA size specification. Use corresponding defines with ``RTE_`` prefix
|
|
|
|
|
instead.
|
|
|
|
|
|
2022-08-04 19:05:56 +00:00
|
|
|
* Removed deprecated ``DEV_RX_OFFLOAD_*`` and ``DEV_TX_OFFLOAD_``
|
|
|
|
|
defines. Use corresponding defines with ``RTE_ETH_RX_OFFLOAD_`` and
|
|
|
|
|
``RTE_ETH_TX_OFFLOAD_`` prefix instead.
|
|
|
|
|
|
2022-08-04 19:05:57 +00:00
|
|
|
* Removed deprecated ``ETH_DCB_*``, ``ETH_VMDQ_``, ``ETH_*_TCS``,
|
|
|
|
|
``ETH_*_POOLS`` and ``ETH_MAX_VMDQ_POOL`` defines. Use corresponding
|
|
|
|
|
defines with ``RTE_`` prefix instead.
|
|
|
|
|
|
2022-08-04 19:05:58 +00:00
|
|
|
* Removed deprecated ``RTE_TUNNEL_*`` defines. Use corresponding
|
|
|
|
|
defines with ``RTE_ETH_TUNNEL_`` prefix instead.
|
|
|
|
|
|
2022-08-04 19:05:59 +00:00
|
|
|
* Removed deprecated ``RTE_FC_*`` defines. Use corresponding
|
|
|
|
|
defines with ``RTE_ETH_FC_`` prefix instead.
|
|
|
|
|
|
2022-08-04 19:06:00 +00:00
|
|
|
* Removed deprecated ``ETH_VLAN_*`` and ``ETH_QINQ_`` defines.
|
|
|
|
|
Use corresponding defines with ``RTE_`` prefix instead.
|
|
|
|
|
|
2022-08-04 19:06:01 +00:00
|
|
|
* Removed deprecated ``ETH_NUM_RECEIVE_MAC_ADDR`` define.
|
|
|
|
|
Use corresponding define with ``RTE_`` prefix instead.
|
|
|
|
|
|
2022-08-04 19:06:02 +00:00
|
|
|
* Removed deprecated ``PKT_{R,T}X_DYNF_METADATA`` defines.
|
|
|
|
|
Use corresponding defines ``RTE_MBUF_DYNFLAG_{R,T}X_METADATA`` instead.
|
|
|
|
|
|
2022-08-03 11:13:58 +00:00
|
|
|
* ethdev: Removed deprecated Flow Director configuration from device
|
|
|
|
|
configuration (``dev_conf.fdir_conf``). Moved corresponding structures
|
|
|
|
|
to internal API since some drivers still use it internally.
|
|
|
|
|
|
2022-08-12 03:13:13 +00:00
|
|
|
* ethdev: Removed the Rx offload flag ``RTE_ETH_RX_OFFLOAD_HEADER_SPLIT``
|
|
|
|
|
and field ``split_hdr_size`` from the structure ``rte_eth_rxmode``
|
|
|
|
|
used to configure header split.
|
|
|
|
|
Instead, user can still use ``RTE_ETH_RX_OFFLOAD_BUFFER_SPLIT``
|
|
|
|
|
for per-queue packet split offload,
|
|
|
|
|
which is configured by ``rte_eth_rxseg_split``.
|
|
|
|
|
|
ethdev: introduce protocol-based buffer split
Currently, Rx buffer split supports length based split. With Rx queue
offload RTE_ETH_RX_OFFLOAD_BUFFER_SPLIT enabled and Rx packet segment
configured, PMD will be able to split the received packets into
multiple segments.
However, length based buffer split is not suitable for NICs that do split
based on protocol headers. Given an arbitrarily variable length in Rx
packet segment, it is almost impossible to pass a fixed protocol header to
driver. Besides, the existence of tunneling results in the composition of
a packet is various, which makes the situation even worse.
This patch extends current buffer split to support protocol header based
buffer split. A new proto_hdr field is introduced in the reserved field
of rte_eth_rxseg_split structure to specify protocol header. The proto_hdr
field defines the split position of packet, splitting will always happen
after the protocol header defined in the Rx packet segment. When Rx queue
offload RTE_ETH_RX_OFFLOAD_BUFFER_SPLIT is enabled and corresponding
protocol header is configured, driver will split the ingress packets into
multiple segments.
Examples for proto_hdr field defines:
To split after ETH-IPV4-UDP, it should be defined as
proto_hdr = RTE_PTYPE_L2_ETHER | RTE_PTYPE_L3_IPV4_EXT_UNKNOWN |
RTE_PTYPE_L4_UDP
For inner ETH-IPV4-UDP, it should be defined as
proto_hdr = RTE_PTYPE_TUNNEL_GRENAT | RTE_PTYPE_INNER_L2_ETHER |
RTE_PTYPE_INNER_L3_IPV4_EXT_UNKNOWN | RTE_PTYPE_INNER_L4_UDP
If the protocol header is repeated with the previously defined one,
the repeated part should be omitted. For example, split after ETH, ETH-IPV4
and ETH-IPV4-UDP, it should be defined as
proto_hdr0 = RTE_PTYPE_L2_ETHER
proto_hdr1 = RTE_PTYPE_L3_IPV4_EXT_UNKNOWN
proto_hdr2 = RTE_PTYPE_L4_UDP
If protocol header split can be supported by a PMD, the
rte_eth_buffer_split_get_supported_hdr_ptypes function can
be used to obtain a list of these protocol headers.
For example, let's suppose we configured the Rx queue with the
following segments:
seg0 - pool0, proto_hdr0=RTE_PTYPE_L2_ETHER | RTE_PTYPE_L3_IPV4,
off0=2B
seg1 - pool1, proto_hdr1=RTE_PTYPE_L4_UDP, off1=128B
seg2 - pool2, proto_hdr2=0, off1=0B
The packet consists of ETH_IPV4_UDP_PAYLOAD will be split like
following:
seg0 - ipv4 header @ RTE_PKTMBUF_HEADROOM + 2 in mbuf from pool0
seg1 - udp header @ 128 in mbuf from pool1
seg2 - payload @ 0 in mbuf from pool2
Now buffer split can be configured in two modes. User can choose length
or protocol header to configure buffer split according to NIC's
capability. For length based buffer split, the mp, length, offset field
in Rx packet segment should be configured, while the proto_hdr field
must be 0. For protocol header based buffer split, the mp, offset,
proto_hdr field in Rx packet segment should be configured, while the
length field must be 0.
Note: When protocol header split is enabled, NIC may receive packets
which do not match all the protocol headers within the Rx segments.
At this point, NIC will have two possible split behaviors according to
matching results, one is exact match, another is longest match.
The split result of NIC must belong to one of them.
The exact match means NIC only do split when the packets exactly match all
the protocol headers in the segments. Otherwise, the whole packet will be
put into the last valid mempool. The longest match means NIC will do split
until packets mismatch the protocol header in the segments. The rest will
be put into the last valid pool.
Pseudo-code for exact match:
FOR each seg in segs except last one
IF proto_hdr is not matched THEN
BREAK
END IF
END FOR
IF loop breaked THEN
put whole pkt in last seg
ELSE
put protocol header in each seg
put everything else in last seg
END IF
Pseudo-code for longest match:
FOR each seg in segs except last one
IF proto_hdr is matched THEN
put protocol header in seg
ELSE
BREAK
END IF
END FOR
put everything else in last seg
Signed-off-by: Yuan Wang <yuanx.wang@intel.com>
Signed-off-by: Xuan Ding <xuan.ding@intel.com>
Signed-off-by: Wenxuan Wu <wenxuanx.wu@intel.com>
Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
2022-10-09 20:25:39 +00:00
|
|
|
* ethdev: The ``reserved`` field in the ``rte_eth_rxseg_split`` structure is
|
|
|
|
|
replaced with ``proto_hdr`` to support protocol header based buffer split.
|
|
|
|
|
User can choose length or protocol header to configure buffer split
|
|
|
|
|
according to NIC's capability.
|
|
|
|
|
|
2022-09-28 05:51:58 +00:00
|
|
|
* ethdev: Changed the type of the parameter ``rate`` of the function
|
|
|
|
|
``rte_eth_set_queue_rate_limit()`` from ``uint16_t`` to ``uint32_t``
|
|
|
|
|
to support more than 64 Gbps.
|
|
|
|
|
Changed the type of the parameter ``tx_rate`` of the functions
|
|
|
|
|
``rte_pmd_bnxt_set_vf_rate_limit()`` and
|
|
|
|
|
``rte_pmd_ixgbe_set_vf_rate_limit()`` in the same way for consistency.
|
|
|
|
|
|
2022-08-12 19:18:15 +00:00
|
|
|
* ethdev: Promoted ``rte_eth_rx_metadata_negotiate()``
|
|
|
|
|
from experimental to stable.
|
|
|
|
|
|
2022-08-12 19:18:16 +00:00
|
|
|
* ethdev: Promoted the following flow primitives
|
|
|
|
|
from experimental to stable:
|
|
|
|
|
|
|
|
|
|
- ``RTE_FLOW_ACTION_TYPE_PORT_REPRESENTOR``
|
|
|
|
|
- ``RTE_FLOW_ACTION_TYPE_REPRESENTED_PORT``
|
|
|
|
|
- ``RTE_FLOW_ITEM_TYPE_PORT_REPRESENTOR``
|
|
|
|
|
- ``RTE_FLOW_ITEM_TYPE_REPRESENTED_PORT``
|
|
|
|
|
|
2022-08-12 19:18:17 +00:00
|
|
|
* ethdev: Promoted ``rte_flow_pick_transfer_proxy()``
|
|
|
|
|
from experimental to stable.
|
|
|
|
|
|
2022-09-30 09:42:48 +00:00
|
|
|
* ethdev: Banned the use of attributes ``ingress``/``egress`` in "transfer"
|
2022-11-24 16:56:10 +00:00
|
|
|
flows, as the final step of the deprecation process that had been started
|
2022-09-30 09:42:48 +00:00
|
|
|
in DPDK 21.11. See items ``PORT_REPRESENTOR``, ``REPRESENTED_PORT``.
|
|
|
|
|
|
2022-10-10 15:37:51 +00:00
|
|
|
* vhost: Promoted ``rte_vhost_vring_stats_get()``,
|
|
|
|
|
``rte_vhost_vring_stats_get_names()`` and ``rte_vhost_vring_stats_reset()``
|
|
|
|
|
from experimental to stable.
|
|
|
|
|
|
2022-10-04 17:37:06 +00:00
|
|
|
* cryptodev: The structure ``rte_cryptodev_sym_session`` was made internal.
|
|
|
|
|
The API ``rte_cryptodev_sym_session_init`` and ``rte_cryptodev_sym_session_clear``
|
|
|
|
|
were removed and user would only need to call ``rte_cryptodev_sym_session_create``
|
|
|
|
|
and ``rte_cryptodev_sym_session_free`` to create/destroy sessions.
|
|
|
|
|
The API ``rte_cryptodev_sym_session_create`` was updated to take a single mempool
|
|
|
|
|
with element size big enough to hold session data and session private data.
|
|
|
|
|
All sample applications were updated to attach an opaque pointer for the session
|
|
|
|
|
to the ``rte_crypto_op`` while enqueuing.
|
|
|
|
|
|
2022-10-04 17:37:09 +00:00
|
|
|
* security: The structure ``rte_security_session`` was made internal
|
|
|
|
|
and corresponding functions were updated to take/return an opaque session pointer.
|
|
|
|
|
The API ``rte_security_session_create`` was updated to take only one mempool
|
|
|
|
|
which has enough space to hold session and driver private data.
|
|
|
|
|
|
2022-11-24 16:56:10 +00:00
|
|
|
* security: MACsec support has been added which resulted in updates
|
2022-09-28 12:22:53 +00:00
|
|
|
to structures ``rte_security_macsec_xform``, ``rte_security_macsec_stats``
|
|
|
|
|
and security capability structure ``rte_security_capability``
|
|
|
|
|
to accommodate MACsec capabilities.
|
|
|
|
|
|
2022-08-12 08:58:36 +00:00
|
|
|
* security: The experimental API ``rte_security_get_userdata`` was being unused
|
|
|
|
|
by most of the drivers and it was retrieving userdata from mbuf dynamic field.
|
|
|
|
|
The API is now removed and the application can directly get the userdata from
|
|
|
|
|
mbuf dynamic field.
|
|
|
|
|
|
2022-10-01 00:42:12 +00:00
|
|
|
* eventdev: The function ``rte_event_crypto_adapter_queue_pair_add`` was updated
|
|
|
|
|
to accept configuration of type ``rte_event_crypto_adapter_queue_conf``
|
|
|
|
|
instead of ``rte_event``,
|
|
|
|
|
similar to ``rte_event_eth_rx_adapter_queue_add`` signature.
|
|
|
|
|
Event will be one of the configuration fields,
|
|
|
|
|
together with additional vector parameters.
|
|
|
|
|
|
2022-10-13 09:15:28 +00:00
|
|
|
* eventdev: The function pointer definition ``eventdev_stop_flush_t``
|
|
|
|
|
is renamed to ``rte_eventdev_stop_flush_t``
|
|
|
|
|
to avoid conflicts with application symbols.
|
|
|
|
|
|
2022-10-13 11:35:01 +00:00
|
|
|
* eventdev: The data type of the ID parameter in the functions
|
|
|
|
|
``rte_event_dev_xstats_names_get``, ``rte_event_dev_xstats_get``,
|
|
|
|
|
``rte_event_dev_xstats_by_name_get`` and ``rte_event_dev_xstats_reset``
|
|
|
|
|
is changed to ``uint64_t`` from ``unsigned int`` and ``uint32_t``.
|
|
|
|
|
|
2022-09-29 09:38:29 +00:00
|
|
|
* metrics: Updated ``rte_metrics_init`` so it returns an error code instead
|
|
|
|
|
of calling ``rte_exit``.
|
|
|
|
|
|
2022-09-09 09:35:19 +00:00
|
|
|
* telemetry: The allowed characters in names for dictionary values
|
|
|
|
|
are now limited to alphanumeric characters and a small subset of additional
|
|
|
|
|
printable characters.
|
|
|
|
|
This will ensure that all dictionary parameter names can be output
|
|
|
|
|
without escaping in JSON - or in any future output format used.
|
|
|
|
|
Names for the telemetry commands are now similarly limited.
|
|
|
|
|
The parameters for telemetry commands are unaffected by this change.
|
|
|
|
|
|
2022-07-28 15:26:17 +00:00
|
|
|
* raw/ifgpa: The function ``rte_pmd_ifpga_get_pci_bus`` has been removed.
|
|
|
|
|
|
2022-07-09 08:43:09 +00:00
|
|
|
|
|
|
|
|
ABI Changes
|
|
|
|
|
-----------
|
|
|
|
|
|
2022-09-26 10:03:14 +00:00
|
|
|
* eal: Updated EAL thread names from ``lcore-worker-<lcore_id>`` to
|
|
|
|
|
``rte-worker-<lcore_id>`` so that DPDK can accommodate lcores higher than 99.
|
|
|
|
|
|
2022-10-07 21:02:09 +00:00
|
|
|
* mbuf: Replaced ``buf_iova`` field with ``next`` field and added a new field
|
|
|
|
|
``dynfield2`` at its place in second cacheline if ``RTE_IOVA_AS_PA`` is 0.
|
|
|
|
|
|
2022-08-12 19:18:24 +00:00
|
|
|
* ethdev: enum ``RTE_FLOW_ITEM`` was affected by deprecation procedure.
|
|
|
|
|
|
2022-08-12 19:18:27 +00:00
|
|
|
* ethdev: enum ``RTE_FLOW_ACTION`` was affected by deprecation procedure.
|
|
|
|
|
|
2022-10-04 17:16:50 +00:00
|
|
|
* bbdev: enum ``rte_bbdev_op_type`` was affected to remove ``RTE_BBDEV_OP_TYPE_COUNT``
|
|
|
|
|
and to allow for futureproof enum insertion a padded ``RTE_BBDEV_OP_TYPE_SIZE_MAX``
|
|
|
|
|
macro is added.
|
|
|
|
|
|
2022-10-04 17:16:51 +00:00
|
|
|
* bbdev: Structure ``rte_bbdev_driver_info`` was updated to add new parameters
|
2022-10-04 17:16:52 +00:00
|
|
|
for queue topology, device status using ``rte_bbdev_device_status``.
|
2022-10-04 17:16:51 +00:00
|
|
|
|
2022-10-04 17:16:55 +00:00
|
|
|
* bbdev: Structure ``rte_bbdev_queue_data`` was updated to add new parameter
|
|
|
|
|
for enqueue status using ``rte_bbdev_enqueue_status``.
|
|
|
|
|
|
2022-09-14 15:33:17 +00:00
|
|
|
* eventdev: Added ``evtim_drop_count`` field
|
|
|
|
|
to ``rte_event_timer_adapter_stats`` structure.
|
|
|
|
|
|
2022-08-10 07:36:52 +00:00
|
|
|
* eventdev: Added ``weight`` and ``affinity`` fields
|
|
|
|
|
to ``rte_event_queue_conf`` structure.
|
|
|
|
|
|
2022-10-13 09:15:28 +00:00
|
|
|
* eventdev: The field ``*u64s`` in the structure ``rte_event_vector`` is replaced
|
2022-11-24 16:56:10 +00:00
|
|
|
with ``u64s`` as the field is supposed to hold an array of ``uint64_t`` values.
|
2022-10-13 09:15:28 +00:00
|
|
|
|
|
|
|
|
* eventdev: The structure ``rte_event_vector`` was updated to include a new bit
|
|
|
|
|
field ``elem_offset:12``. The bits are taken from the bitfield ``rsvd:15``.
|
|
|
|
|
|
2022-07-09 08:43:09 +00:00
|
|
|
|
|
|
|
|
Tested Platforms
|
|
|
|
|
----------------
|
|
|
|
|
|
2022-11-17 04:36:02 +00:00
|
|
|
* Intel\ |reg| platforms with Intel\ |reg| NICs combinations
|
|
|
|
|
|
|
|
|
|
* CPU
|
|
|
|
|
|
|
|
|
|
* Intel\ |reg| Atom\ |trade| CPU C3758 @ 2.20GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| CPU D-1553N @ 2.30GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| CPU E5-2680 v2 @ 2.80GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| CPU E5-2699 v3 @ 2.30GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| CPU E5-2699 v4 @ 2.20GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| D-2796NT CPU @ 2.00GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| Gold 6139 CPU @ 2.30GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| Gold 6140M CPU @ 2.30GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| Gold 6252N CPU @ 2.30GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| Gold 6348 CPU @ 2.60GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| Platinum 8180M CPU @ 2.50GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| Platinum 8280M CPU @ 2.70GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| Platinum 8380 CPU @ 2.30GHz
|
|
|
|
|
|
|
|
|
|
* OS:
|
|
|
|
|
|
|
|
|
|
* Fedora 36
|
|
|
|
|
* FreeBSD 13.1
|
|
|
|
|
* Red Hat Enterprise Linux Server release 8.6
|
|
|
|
|
* Red Hat Enterprise Linux Server release 9
|
|
|
|
|
* CentOS 7.9
|
|
|
|
|
* Ubuntu 20.04.5
|
|
|
|
|
* Ubuntu 22.04.1
|
|
|
|
|
* Ubuntu 22.10
|
|
|
|
|
* SUSE Linux Enterprise Server 15 SP4
|
|
|
|
|
|
|
|
|
|
* NICs:
|
|
|
|
|
|
|
|
|
|
* Intel\ |reg| Ethernet Controller E810-C for SFP (4x25G)
|
|
|
|
|
|
|
|
|
|
* Firmware version: 4.10 0x800151d8 1.3310.0
|
|
|
|
|
* Device id (pf/vf): 8086:1593 / 8086:1889
|
|
|
|
|
* Driver version(out-tree): 1.10.6 (ice)
|
|
|
|
|
* Driver version(in-tree): 5.15.0-46-generic / 4.18.0-372.9.1.rt7.166.el8.x86_64 (ice)
|
|
|
|
|
* OS Default DDP: 1.3.30.0
|
|
|
|
|
* COMMS DDP: 1.3.37.0
|
|
|
|
|
* Wireless Edge DDP: 1.3.10.0
|
|
|
|
|
|
|
|
|
|
* Intel\ |reg| Ethernet Controller E810-C for QSFP (2x100G)
|
|
|
|
|
|
|
|
|
|
* Firmware version: 4.10 0x8001518e 1.3310.0
|
|
|
|
|
* Device id (pf/vf): 8086:1592 / 8086:1889
|
|
|
|
|
* Driver version: 1.10.6 (ice)
|
|
|
|
|
* OS Default DDP: 1.3.30.0
|
|
|
|
|
* COMMS DDP: 1.3.37.0
|
|
|
|
|
* Wireless Edge DDP: 1.3.10.0
|
|
|
|
|
|
|
|
|
|
* Intel\ |reg| Ethernet Controller E810-XXV for SFP (2x25G)
|
|
|
|
|
|
|
|
|
|
* Firmware version: 4.10 0x80015188 1.3310.0
|
|
|
|
|
* Device id (pf/vf): 8086:159b / 8086:1889
|
|
|
|
|
* Driver version: 1.10.6 (ice)
|
|
|
|
|
* OS Default DDP: 1.3.30.0
|
|
|
|
|
* COMMS DDP: 1.3.37.0
|
|
|
|
|
|
|
|
|
|
* Intel\ |reg| 82599ES 10 Gigabit Ethernet Controller
|
|
|
|
|
|
|
|
|
|
* Firmware version: 0x61bf0001
|
|
|
|
|
* Device id (pf/vf): 8086:10fb / 8086:10ed
|
|
|
|
|
* Driver version(out-tree): 5.16.5 (ixgbe)
|
|
|
|
|
* Driver version(in-tree): 5.15.0-46-generic (ixgbe)
|
|
|
|
|
|
|
|
|
|
* Intel\ |reg| Ethernet Converged Network Adapter X710-DA4 (4x10G)
|
|
|
|
|
|
|
|
|
|
* Firmware version: 9.00 0x8000cead 1.3179.0
|
|
|
|
|
* Device id (pf/vf): 8086:1572 / 8086:154c
|
|
|
|
|
* Driver version(out-tree): 2.20.12 (i40e)
|
|
|
|
|
* Driver version(in-tree): 5.15.0-46-generic (i40e)
|
|
|
|
|
|
|
|
|
|
* Intel\ |reg| Corporation Ethernet Connection X722 for 10GbE SFP+ (2x10G)
|
|
|
|
|
|
|
|
|
|
* Firmware version: 6.00 0x800039ec 1.3179.0
|
|
|
|
|
* Device id (pf/vf): 8086:37d0 / 8086:37cd
|
|
|
|
|
* Driver version(out-tree): 2.20.12 (i40e)
|
|
|
|
|
* Driver version(in-tree): 5.15.0-46-generic (i40e)
|
|
|
|
|
|
|
|
|
|
* Intel\ |reg| Corporation Ethernet Connection X722 for 10GBASE-T
|
|
|
|
|
|
|
|
|
|
* Firmware version: 6.00 0x800039aa 1.2935.0
|
|
|
|
|
* Device id (pf/vf): 8086:37d2 / 8086:37cd
|
|
|
|
|
* Driver version(out-tree): 2.20.12 (i40e)
|
|
|
|
|
* Driver version(in-tree): 5.15.0-46-generic (i40e)
|
|
|
|
|
|
|
|
|
|
* Intel\ |reg| Ethernet Converged Network Adapter XXV710-DA2 (2x25G)
|
|
|
|
|
|
|
|
|
|
* Firmware version: 9.00 0x8000ce90 1.3179.0
|
|
|
|
|
* Device id (pf/vf): 8086:158b / 8086:154c
|
|
|
|
|
* Driver version(out-tree): 2.20.12 (i40e)
|
|
|
|
|
* Driver version(in-tree): 5.15.0-46-generic (i40e)
|
|
|
|
|
|
|
|
|
|
* Intel\ |reg| Ethernet Converged Network Adapter XL710-QDA2 (2X40G)
|
|
|
|
|
|
|
|
|
|
* Firmware version(PF): 9.00 0x8000ce86 1.3179.0
|
|
|
|
|
* Device id (pf/vf): 8086:1583 / 8086:154c
|
|
|
|
|
* Driver version(out-tree): 2.20.12 (i40e)
|
|
|
|
|
* Driver version(in-tree): 5.15.0-46-generic (i40e)
|
|
|
|
|
|
|
|
|
|
* Intel\ |reg| Ethernet Converged Network Adapter X710-T2L
|
|
|
|
|
|
|
|
|
|
* Firmware version: 9.00 0x8000ce67 1.3179.0
|
|
|
|
|
* Device id (pf): 8086:15ff
|
|
|
|
|
* Driver version: 2.20.12 (i40e)
|
2022-11-21 09:10:02 +00:00
|
|
|
|
|
|
|
|
* Intel\ |reg| platforms with NVIDIA\ |reg| NICs combinations
|
|
|
|
|
|
|
|
|
|
* CPU:
|
|
|
|
|
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| Gold 6154 CPU @ 3.00GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| CPU E5-2697A v4 @ 2.60GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| CPU E5-2697 v3 @ 2.60GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| CPU E5-2680 v2 @ 2.80GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| CPU E5-2670 0 @ 2.60GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| CPU E5-2650 v4 @ 2.20GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| CPU E5-2650 v3 @ 2.30GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| CPU E5-2640 @ 2.50GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| CPU E5-2650 0 @ 2.00GHz
|
|
|
|
|
* Intel\ |reg| Xeon\ |reg| CPU E5-2620 v4 @ 2.10GHz
|
|
|
|
|
|
|
|
|
|
* OS:
|
|
|
|
|
|
|
|
|
|
* Red Hat Enterprise Linux release 8.6 (Ootpa)
|
|
|
|
|
* Red Hat Enterprise Linux release 8.4 (Ootpa)
|
|
|
|
|
* Red Hat Enterprise Linux release 8.2 (Ootpa)
|
|
|
|
|
* Red Hat Enterprise Linux Server release 7.9 (Maipo)
|
|
|
|
|
* Red Hat Enterprise Linux Server release 7.8 (Maipo)
|
|
|
|
|
* Red Hat Enterprise Linux Server release 7.6 (Maipo)
|
|
|
|
|
* Red Hat Enterprise Linux Server release 7.5 (Maipo)
|
|
|
|
|
* Red Hat Enterprise Linux Server release 7.4 (Maipo)
|
|
|
|
|
* Ubuntu 22.04
|
|
|
|
|
* Ubuntu 20.04
|
|
|
|
|
* Ubuntu 18.04
|
|
|
|
|
* SUSE Enterprise Linux 15 SP2
|
|
|
|
|
|
|
|
|
|
* OFED:
|
|
|
|
|
|
|
|
|
|
* MLNX_OFED 5.8-1.0.1.1 and above
|
|
|
|
|
* MLNX_OFED 5.7-1.0.2.0
|
|
|
|
|
|
|
|
|
|
* upstream kernel:
|
|
|
|
|
|
|
|
|
|
* Linux 6.1.0-rc3 and above
|
|
|
|
|
|
|
|
|
|
* rdma-core:
|
|
|
|
|
|
|
|
|
|
* rdma-core-43.0 and above
|
|
|
|
|
|
|
|
|
|
* NICs:
|
|
|
|
|
|
|
|
|
|
* NVIDIA\ |reg| ConnectX\ |reg|-3 Pro 40G MCX354A-FCC_Ax (2x40G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x8
|
|
|
|
|
* Device ID: 15b3:1007
|
|
|
|
|
* Firmware version: 2.42.5000
|
|
|
|
|
|
|
|
|
|
* NVIDIA\ |reg| ConnectX\ |reg|-3 Pro 40G MCX354A-FCCT (2x40G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x8
|
|
|
|
|
* Device ID: 15b3:1007
|
|
|
|
|
* Firmware version: 2.42.5000
|
|
|
|
|
|
|
|
|
|
* NVIDIA\ |reg| ConnectX\ |reg|-4 Lx 25G MCX4121A-ACAT (2x25G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x8
|
|
|
|
|
* Device ID: 15b3:1015
|
|
|
|
|
* Firmware version: 14.32.1010 and above
|
|
|
|
|
|
|
|
|
|
* NVIDIA\ |reg| ConnectX\ |reg|-4 Lx 50G MCX4131A-GCAT (1x50G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x8
|
|
|
|
|
* Device ID: 15b3:1015
|
|
|
|
|
* Firmware version: 14.32.1010 and above
|
|
|
|
|
|
|
|
|
|
* NVIDIA\ |reg| ConnectX\ |reg|-5 100G MCX516A-CCAT (2x100G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x16
|
|
|
|
|
* Device ID: 15b3:1017
|
|
|
|
|
* Firmware version: 16.35.1012 and above
|
|
|
|
|
|
|
|
|
|
* NVIDIA\ |reg| ConnectX\ |reg|-5 100G MCX556A-ECAT (2x100G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x16
|
|
|
|
|
* Device ID: 15b3:1017
|
|
|
|
|
* Firmware version: 16.35.1012 and above
|
|
|
|
|
|
|
|
|
|
* NVIDIA\ |reg| ConnectX\ |reg|-5 100G MCX556A-EDAT (2x100G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x16
|
|
|
|
|
* Device ID: 15b3:1017
|
|
|
|
|
* Firmware version: 16.35.1012 and above
|
|
|
|
|
|
|
|
|
|
* NVIDIA\ |reg| ConnectX\ |reg|-5 Ex EN 100G MCX516A-CDAT (2x100G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 4.0 x16
|
|
|
|
|
* Device ID: 15b3:1019
|
|
|
|
|
* Firmware version: 16.35.1012 and above
|
|
|
|
|
|
|
|
|
|
* NVIDIA\ |reg| ConnectX\ |reg|-6 Dx EN 100G MCX623106AN-CDAT (2x100G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 4.0 x16
|
|
|
|
|
* Device ID: 15b3:101d
|
|
|
|
|
* Firmware version: 22.35.1012 and above
|
|
|
|
|
|
|
|
|
|
* NVIDIA\ |reg| ConnectX\ |reg|-6 Lx EN 25G MCX631102AN-ADAT (2x25G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 4.0 x8
|
|
|
|
|
* Device ID: 15b3:101f
|
|
|
|
|
* Firmware version: 26.35.1012 and above
|
|
|
|
|
|
|
|
|
|
* NVIDIA\ |reg| ConnectX\ |reg|-7 200G CX713106AE-HEA_QP1_Ax (2x200G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 5.0 x16
|
|
|
|
|
* Device ID: 15b3:1021
|
|
|
|
|
* Firmware version: 28.35.1012 and above
|
|
|
|
|
|
|
|
|
|
* NVIDIA\ |reg| BlueField\ |reg| SmartNIC
|
|
|
|
|
|
|
|
|
|
* NVIDIA\ |reg| BlueField\ |reg|-2 SmartNIC MT41686 - MBF2H332A-AEEOT_A1 (2x25G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 3.0 x16
|
|
|
|
|
* Device ID: 15b3:a2d6
|
|
|
|
|
* Firmware version: 24.35.1012 and above
|
|
|
|
|
|
|
|
|
|
* Embedded software:
|
|
|
|
|
|
|
|
|
|
* Ubuntu 20.04.3
|
|
|
|
|
* MLNX_OFED 5.8-1.0.1.1 and above
|
|
|
|
|
* DOCA 1.5 with BlueField 3.9.3
|
|
|
|
|
* DPDK application running on ARM cores
|
|
|
|
|
|
|
|
|
|
* IBM Power 9 platforms with NVIDIA\ |reg| NICs combinations
|
|
|
|
|
|
|
|
|
|
* CPU:
|
|
|
|
|
|
|
|
|
|
* POWER9 2.2 (pvr 004e 1202)
|
|
|
|
|
|
|
|
|
|
* OS:
|
|
|
|
|
|
|
|
|
|
* Ubuntu 20.04
|
|
|
|
|
|
|
|
|
|
* NICs:
|
|
|
|
|
|
|
|
|
|
* NVIDIA\ |reg| ConnectX\ |reg|-5 100G MCX556A-ECAT (2x100G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 4.0 x16
|
|
|
|
|
* Device ID: 15b3:1017
|
|
|
|
|
* Firmware version: 16.35.1012
|
|
|
|
|
|
|
|
|
|
* NVIDIA\ |reg| ConnectX\ |reg|-6 Dx 100G MCX623106AN-CDAT (2x100G)
|
|
|
|
|
|
|
|
|
|
* Host interface: PCI Express 4.0 x16
|
|
|
|
|
* Device ID: 15b3:101d
|
|
|
|
|
* Firmware version: 22.35.1012
|
|
|
|
|
|
|
|
|
|
* OFED:
|
|
|
|
|
|
|
|
|
|
* MLNX_OFED 5.8-1.0.1.1
|
