X-Git-Url: http://git.droids-corp.org/?a=blobdiff_plain;f=doc%2Fguides%2Frel_notes%2Frelease_19_02.rst;h=b353620b728ad5d531bc0b57fffcea6a0f44d5da;hb=65661351caa8f54740cdf4b67f3b7e888b8fca34;hp=fb0cf8bd2f00bd837ffdc1673f27078d3b362095;hpb=f173fd74c0181751fc98b661eca87ae1bf55befe;p=dpdk.git diff --git a/doc/guides/rel_notes/release_19_02.rst b/doc/guides/rel_notes/release_19_02.rst index fb0cf8bd2f..b353620b72 100644 --- a/doc/guides/rel_notes/release_19_02.rst +++ b/doc/guides/rel_notes/release_19_02.rst @@ -54,7 +54,7 @@ New Features Also, make sure to start the actual text at the margin. ========================================================= -* **Added support to free hugepages exactly as originally allocated.** +* **Added support for freeing hugepages exactly as originally allocated.** Some applications using memory event callbacks (especially for managing RDMA memory regions) require that memory be freed back to the system @@ -69,16 +69,19 @@ New Features chunks of external memory to be registered with DPDK without adding them to the malloc heap. -* **Support for using virtio-user without hugepages** +* **Added support for using virtio-user without hugepages.** - The --no-huge mode was augmented to use memfd-backed memory (on systems that - support memfd), to allow using virtio-user-based NICs without hugepages. + The ``--no-huge`` mode was augmented to use memfd-backed memory (on systems + that support memfd), to allow using virtio-user-based NICs without + hugepages. -* **Release of the ENA PMD v2.0.0** +* **Release of the ENA PMD v2.0.0.** + + Version 2.0.0 of the ENA PMD was added with the following additions: * Added Low Latency Queue v2 (LLQv2). This feature reduces the latency of the packets by pushing the header directly through the PCI to the - device. This allows the NIC to start handle packet right after the doorbell + device. This allows the NIC to start handle packets right after the doorbell without waiting for DMA. * Added independent configuration of HW Tx and Rx ring depths. * Added support for up to 8k Rx descriptors per ring. @@ -93,33 +96,49 @@ New Features traffic. * Updated documentation and features list of the PMD. +* **Updated mlx5 driver.** + + Updated the mlx5 driver including the following changes: + + * Fixed ``imissed`` counter to be reported through ``rte_eth_stats`` instead + of ``rte_eth_xstats``. + * Added packet header modification through Direct Verbs flow driver. + * Added ConnectX-6 PCI device ID to be proved by ``mlx5`` driver. + * Added flow counter support to Direct Verbs flow driver though DevX. + * Renamed build options for the glue layer to + ``CONFIG_RTE_IBVERBS_LINK_DLOPEN`` for make and ``ibverbs_link`` for meson. + * Added static linkage of ``mlx`` dependency. + * Improved stability of E-Switch flow driver. + * Added new make build configuration to set the cacheline size for Bluefield + correctly - ``arm64-bluefield-linux-gcc``. + * **Updated the enic driver.** - * Added support for ``RTE_ETH_DEV_CLOSE_REMOVE`` flag. - * Added the handler to get firmware version string. + * Added support for the ``RTE_ETH_DEV_CLOSE_REMOVE`` flag. + * Added a handler to get the firmware version string. * Added support for multicast filtering. * **Added dynamic queues allocation support for i40e VF.** - Previously, available queues of VF is reserved by PF at initialize stage. - Now both DPDK PF and Kernel PF (>=2.1.14) will support dynamic queue - allocation. At runtime, when VF request more queue number exceed the initial - reserved amount, PF can allocate up to 16 queues as the request after a VF - reset. + Previously, the available VF queues were reserved by PF at initialization + stage. Now both DPDK PF and Kernel PF (>=2.1.14) will support dynamic queue + allocation. At runtime, when VF requests for more queue exceed the initial + reserved amount, the PF can allocate up to 16 queues as the request after a + VF reset. -* **Added ICE net PMD** +* **Added ICE net PMD.** - Added the new ``ice`` net driver for Intel® Ethernet Network Adapters E810. + Added the new ``ice`` net driver for Intel(R) Ethernet Network Adapters E810. See the :doc:`../nics/ice` NIC guide for more details on this new driver. * **Added support for SW-assisted VDPA live migration.** This SW-assisted VDPA live migration facility helps VDPA devices without logging capability to perform live migration, a mediated SW relay can help - devices to track dirty pages caused by DMA. IFC driver has enabled this + devices to track dirty pages caused by DMA. the IFC driver has enabled this SW-assisted live migration mode. -* **Added security checks to cryptodev symmetric session operations.** +* **Added security checks to the cryptodev symmetric session operations.** Added a set of security checks to the access cryptodev symmetric session. The checks include the session's user data read/write check and the @@ -127,9 +146,9 @@ New Features * **Updated the AESNI-MB PMD.** - * Add support for intel-ipsec-mb version 0.52. - * Add AES-GMAC algorithm support. - * Add Plain SHA1, SHA224, SHA256, SHA384, and SHA512 algorithms support. + * Added support for intel-ipsec-mb version 0.52. + * Added AES-GMAC algorithm support. + * Added Plain SHA1, SHA224, SHA256, SHA384, and SHA512 algorithms support. * **Added IPsec Library.** @@ -145,13 +164,13 @@ New Features * **Updated the ipsec-secgw sample application.** The ``ipsec-secgw`` sample application has been updated to use the new - ``librte_ipsec`` library also added in this release. + ``librte_ipsec`` library, which has also been added in this release. The original functionality of ipsec-secgw is retained, a new command line parameter ``-l`` has been added to ipsec-secgw to use the IPsec library, instead of the existing IPsec code in the application. The IPsec library does not support all the functionality of the existing - ipsec-secgw application, its is planned to add the outstanding functionality + ipsec-secgw application. It is planned to add the outstanding functionality in future releases. See :doc:`../sample_app_ug/ipsec_secgw` for more information. @@ -175,19 +194,6 @@ New Features detected by the library. -Removed Items -------------- - -.. This section should contain removed items in this release. Sample format: - - * Add a short 1-2 sentence description of the removed item - in the past tense. - - This section is a comment. Do not overwrite or remove it. - Also, make sure to start the actual text at the margin. - ========================================================= - - API Changes ----------- @@ -204,16 +210,16 @@ API Changes ========================================================= * eal: Function ``rte_bsf64`` in ``rte_bitmap.h`` has been renamed to - ``rte_bsf64_safe`` and moved to ``rte_common.h``. A new ``rte_bsf64`` function - has been added in ``rte_common.h`` that follows convention set by existing - ``rte_bsf32`` function. + ``rte_bsf64_safe`` and moved to ``rte_common.h``. A new ``rte_bsf64`` + function has been added in ``rte_common.h`` that follows the convention set + by the existing ``rte_bsf32`` function. * eal: Segment fd API on Linux now sets error code to ``ENOTSUP`` in more cases - where segment fd API is not expected to be supported: + where segment the fd API is not expected to be supported: - - On attempt to get segment fd for an externally allocated memory segment + - On attempt to get a segment fd for an externally allocated memory segment - In cases where memfd support would have been required to provide segment - fd's (such as in-memory or no-huge mode) + fds (such as in-memory or no-huge mode) * eal: Functions ``rte_malloc_dump_stats()``, ``rte_malloc_dump_heaps()`` and ``rte_malloc_get_socket_stats()`` are no longer safe to call concurrently with @@ -234,10 +240,10 @@ API Changes * cryptodev: The parameter ``session_pool`` in the function ``rte_cryptodev_queue_pair_setup()`` is removed. -* cryptodev: a new function ``rte_cryptodev_sym_session_pool_create()`` is +* cryptodev: a new function ``rte_cryptodev_sym_session_pool_create()`` has been introduced. This function is now mandatory when creating symmetric session header mempool. Please note all crypto applications are required to use this - function from now on. Failed to do so will cause + function from now on. Failed to do so will cause a ``rte_cryptodev_sym_session_create()`` function call return error. @@ -260,14 +266,14 @@ ABI Changes to include the following fields: ``queue ID``, ``traffic class``, ``color``. * cryptodev: as shown in the the 18.11 deprecation notice, the structure - ``rte_cryptodev_qp_conf`` has been added two parameters of symmetric session + ``rte_cryptodev_qp_conf`` has added two parameters for symmetric session mempool and symmetric session private data mempool. * cryptodev: as shown in the the 18.11 deprecation notice, the structure ``rte_cryptodev_sym_session`` has been updated to contain more information to ensure safely accessing the session and session private data. -* security: New field ``uint64_t opaque_data`` is added into +* security: A new field ``uint64_t opaque_data`` has been added to ``rte_security_session`` structure. That would allow upper layer to easily associate/de-associate some user defined data with the security session. @@ -469,3 +475,191 @@ Tested Platforms * Firmware version: 1.63, 0x80000dda * Device id (pf/vf): 8086:1521 / 8086:1520 * Driver version: 5.4.0-k (igb) + +* Intel(R) platforms with Mellanox(R) NICs combinations + + * CPU: + + * Intel(R) Xeon(R) Gold 6154 CPU @ 3.00GHz + * Intel(R) Xeon(R) CPU E5-2697A v4 @ 2.60GHz + * Intel(R) Xeon(R) CPU E5-2697 v3 @ 2.60GHz + * Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz + * Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz + * Intel(R) Xeon(R) CPU E5-2640 @ 2.50GHz + * Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz + + * OS: + + * 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) + * Red Hat Enterprise Linux Server release 7.3 (Maipo) + * Red Hat Enterprise Linux Server release 7.2 (Maipo) + * Ubuntu 18.10 + * Ubuntu 18.04 + * Ubuntu 17.10 + * Ubuntu 16.04 + * SUSE Linux Enterprise Server 15 + + * MLNX_OFED: 4.4-2.0.1.0 + * MLNX_OFED: 4.5-1.0.1.0 + + * NICs: + + * Mellanox(R) ConnectX(R)-3 Pro 40G MCX354A-FCC_Ax (2x40G) + + * Host interface: PCI Express 3.0 x8 + * Device ID: 15b3:1007 + * Firmware version: 2.42.5000 + + * Mellanox(R) ConnectX(R)-4 10G MCX4111A-XCAT (1x10G) + + * Host interface: PCI Express 3.0 x8 + * Device ID: 15b3:1013 + * Firmware version: 12.24.1000 and above + + * Mellanox(R) ConnectX(R)-4 10G MCX4121A-XCAT (2x10G) + + * Host interface: PCI Express 3.0 x8 + * Device ID: 15b3:1013 + * Firmware version: 12.24.1000 and above + + * Mellanox(R) ConnectX(R)-4 25G MCX4111A-ACAT (1x25G) + + * Host interface: PCI Express 3.0 x8 + * Device ID: 15b3:1013 + * Firmware version: 12.24.1000 and above + + * Mellanox(R) ConnectX(R)-4 25G MCX4121A-ACAT (2x25G) + + * Host interface: PCI Express 3.0 x8 + * Device ID: 15b3:1013 + * Firmware version: 12.24.1000 and above + + * Mellanox(R) ConnectX(R)-4 40G MCX4131A-BCAT/MCX413A-BCAT (1x40G) + + * Host interface: PCI Express 3.0 x8 + * Device ID: 15b3:1013 + * Firmware version: 12.24.1000 and above + + * Mellanox(R) ConnectX(R)-4 40G MCX415A-BCAT (1x40G) + + * Host interface: PCI Express 3.0 x16 + * Device ID: 15b3:1013 + * Firmware version: 12.24.1000 and above + + * Mellanox(R) ConnectX(R)-4 50G MCX4131A-GCAT/MCX413A-GCAT (1x50G) + + * Host interface: PCI Express 3.0 x8 + * Device ID: 15b3:1013 + * Firmware version: 12.24.1000 and above + + * Mellanox(R) ConnectX(R)-4 50G MCX414A-BCAT (2x50G) + + * Host interface: PCI Express 3.0 x8 + * Device ID: 15b3:1013 + * Firmware version: 12.24.1000 and above + + * Mellanox(R) ConnectX(R)-4 50G MCX415A-GCAT/MCX416A-BCAT/MCX416A-GCAT (2x50G) + + * Host interface: PCI Express 3.0 x16 + * Device ID: 15b3:1013 + * Firmware version: 12.24.1000 and above + * Firmware version: 12.24.1000 and above + + * Mellanox(R) ConnectX(R)-4 50G MCX415A-CCAT (1x100G) + + * Host interface: PCI Express 3.0 x16 + * Device ID: 15b3:1013 + * Firmware version: 12.24.1000 and above + + * Mellanox(R) ConnectX(R)-4 100G MCX416A-CCAT (2x100G) + + * Host interface: PCI Express 3.0 x16 + * Device ID: 15b3:1013 + * Firmware version: 12.24.1000 and above + + * Mellanox(R) ConnectX(R)-4 Lx 10G MCX4121A-XCAT (2x10G) + + * Host interface: PCI Express 3.0 x8 + * Device ID: 15b3:1015 + * Firmware version: 14.24.1000 and above + + * Mellanox(R) ConnectX(R)-4 Lx 25G MCX4121A-ACAT (2x25G) + + * Host interface: PCI Express 3.0 x8 + * Device ID: 15b3:1015 + * Firmware version: 14.24.1000 and above + + * Mellanox(R) ConnectX(R)-5 100G MCX556A-ECAT (2x100G) + + * Host interface: PCI Express 3.0 x16 + * Device ID: 15b3:1017 + * Firmware version: 16.24.1000 and above + + * Mellanox(R) ConnectX(R)-5 Ex EN 100G MCX516A-CDAT (2x100G) + + * Host interface: PCI Express 4.0 x16 + * Device ID: 15b3:1019 + * Firmware version: 16.24.1000 and above + +* ARM platforms with Mellanox(R) NICs combinations + + * CPU: + + * Qualcomm ARM 1.1 2500MHz + + * OS: + + * Red Hat Enterprise Linux Server release 7.5 (Maipo) + + * NICs: + + * Mellanox(R) ConnectX(R)-4 Lx 25G MCX4121A-ACAT (2x25G) + + * Host interface: PCI Express 3.0 x8 + * Device ID: 15b3:1015 + * Firmware version: 14.24.0220 + + * Mellanox(R) ConnectX(R)-5 100G MCX556A-ECAT (2x100G) + + * Host interface: PCI Express 3.0 x16 + * Device ID: 15b3:1017 + * Firmware version: 16.24.0220 + +* Mellanox(R) BlueField SmartNIC + + * Mellanox(R) BlueField SmartNIC MT416842 (2x25G) + + * Host interface: PCI Express 3.0 x16 + * Device ID: 15b3:a2d2 + * Firmware version: 18.24.0328 + + * SoC ARM cores running OS: + + * CentOS Linux release 7.4.1708 (AltArch) + * MLNX_OFED 4.4-2.5.9.0 + + * DPDK application running on ARM cores inside SmartNIC + +* Power 9 platforms with Mellanox(R) NICs combinations + + * CPU: + + * POWER9 2.2 (pvr 004e 1202) 2300MHz + + * OS: + + * Ubuntu 18.04.1 LTS (Bionic Beaver) + + * NICs: + + * Mellanox(R) ConnectX(R)-5 100G MCX556A-ECAT (2x100G) + + * Host interface: PCI Express 3.0 x16 + * Device ID: 15b3:1017 + * Firmware version: 16.23.1020 + + * OFED: + + * MLNX_OFED_LINUX-4.5-1.0.1.0