1.. SPDX-License-Identifier: BSD-3-Clause 2 Copyright 2018 The DPDK contributors 3 4DPDK Release 19.02 5================== 6 7.. **Read this first.** 8 9 The text in the sections below explains how to update the release notes. 10 11 Use proper spelling, capitalization and punctuation in all sections. 12 13 Variable and config names should be quoted as fixed width text: 14 ``LIKE_THIS``. 15 16 Build the docs and view the output file to ensure the changes are correct:: 17 18 make doc-guides-html 19 20 xdg-open build/doc/html/guides/rel_notes/release_19_02.html 21 22 23New Features 24------------ 25 26.. This section should contain new features added in this release. 27 Sample format: 28 29 * **Add a title in the past tense with a full stop.** 30 31 Add a short 1-2 sentence description in the past tense. 32 The description should be enough to allow someone scanning 33 the release notes to understand the new feature. 34 35 If the feature adds a lot of sub-features you can use a bullet list 36 like this: 37 38 * Added feature foo to do something. 39 * Enhanced feature bar to do something else. 40 41 Refer to the previous release notes for examples. 42 43 Suggested order in release notes items: 44 * Core libs (EAL, mempool, ring, mbuf, buses) 45 * Device abstraction libs and PMDs 46 - ethdev (lib, PMDs) 47 - cryptodev (lib, PMDs) 48 - eventdev (lib, PMDs) 49 - etc 50 * Other libs 51 * Apps, Examples, Tools (if significant) 52 53 This section is a comment. Do not overwrite or remove it. 54 Also, make sure to start the actual text at the margin. 55 ========================================================= 56 57* **Added support for freeing hugepages exactly as originally allocated.** 58 59 Some applications using memory event callbacks (especially for managing 60 RDMA memory regions) require that memory be freed back to the system 61 exactly as it was originally allocated. These applications typically 62 also require that a malloc allocation not span across two separate 63 hugepage allocations. A new ``--match-allocations`` EAL init flag has 64 been added to fulfill both of these requirements. 65 66* **Added API to register external memory in DPDK.** 67 68 A new ``rte_extmem_register``/``rte_extmem_unregister`` API was added to allow 69 chunks of external memory to be registered with DPDK without adding them to 70 the malloc heap. 71 72* **Added support for using virtio-user without hugepages.** 73 74 The ``--no-huge`` mode was augmented to use memfd-backed memory (on systems 75 that support memfd), to allow using virtio-user-based NICs without 76 hugepages. 77 78* **Release of the ENA PMD v2.0.0.** 79 80 Version 2.0.0 of the ENA PMD was added with the following additions: 81 82 * Added Low Latency Queue v2 (LLQv2). This feature reduces the latency 83 of the packets by pushing the header directly through the PCI to the 84 device. This allows the NIC to start handle packets right after the doorbell 85 without waiting for DMA. 86 * Added independent configuration of HW Tx and Rx ring depths. 87 * Added support for up to 8k Rx descriptors per ring. 88 * Added additional doorbell check on Tx, to handle Tx more efficiently for big 89 bursts of packets. 90 * Added per queue statistics. 91 * Added extended statistics using xstats DPDK API. 92 * The reset routine was aligned with the DPDK API, so now it can be 93 handled as in other PMDs. 94 * Fixed out of order (OOO) completion. 95 * Fixed memory leaks due to port stops and starts in the middle of 96 traffic. 97 * Updated documentation and features list of the PMD. 98 99* **Updated mlx5 driver.** 100 101 Updated the mlx5 driver including the following changes: 102 103 * Fixed ``imissed`` counter to be reported through ``rte_eth_stats`` instead 104 of ``rte_eth_xstats``. 105 * Added packet header modification through Direct Verbs flow driver. 106 * Added ConnectX-6 PCI device ID to be proved by ``mlx5`` driver. 107 * Added flow counter support to Direct Verbs flow driver though DevX. 108 * Renamed build options for the glue layer to 109 ``CONFIG_RTE_IBVERBS_LINK_DLOPEN`` for make and ``ibverbs_link`` for meson. 110 * Added static linkage of ``mlx`` dependency. 111 * Improved stability of E-Switch flow driver. 112 * Added new make build configuration to set the cacheline size for BlueField 113 correctly - ``arm64-bluefield-linux-gcc``. 114 115* **Updated the enic driver.** 116 117 * Added support for the ``RTE_ETH_DEV_CLOSE_REMOVE`` flag. 118 * Added a handler to get the firmware version string. 119 * Added support for multicast filtering. 120 121* **Added dynamic queues allocation support for i40e VF.** 122 123 Previously, the available VF queues were reserved by PF at initialization 124 stage. Now both DPDK PF and Kernel PF (>=2.1.14) will support dynamic queue 125 allocation. At runtime, when VF requests for more queue exceed the initial 126 reserved amount, the PF can allocate up to 16 queues as the request after a 127 VF reset. 128 129* **Added ICE net PMD.** 130 131 Added the new ``ice`` net driver for Intel(R) Ethernet Network Adapters E810. 132 See the :doc:`../nics/ice` NIC guide for more details on this new driver. 133 134* **Added support for SW-assisted VDPA live migration.** 135 136 This SW-assisted VDPA live migration facility helps VDPA devices without 137 logging capability to perform live migration, a mediated SW relay can help 138 devices to track dirty pages caused by DMA. the IFC driver has enabled this 139 SW-assisted live migration mode. 140 141* **Added security checks to the cryptodev symmetric session operations.** 142 143 Added a set of security checks to the access cryptodev symmetric session. 144 The checks include the session's user data read/write check and the 145 session private data referencing status check while freeing a session. 146 147* **Updated the AESNI-MB PMD.** 148 149 * Added support for intel-ipsec-mb version 0.52. 150 * Added AES-GMAC algorithm support. 151 * Added Plain SHA1, SHA224, SHA256, SHA384, and SHA512 algorithms support. 152 153* **Added IPsec Library.** 154 155 Added an experimental library ``librte_ipsec`` to provide ESP tunnel and 156 transport support for IPv4 and IPv6 packets. 157 158 The library provides support for AES-CBC ciphering and AES-CBC with HMAC-SHA1 159 algorithm-chaining, and AES-GCM and NULL algorithms only at present. It is 160 planned to add more algorithms in future releases. 161 162 See :doc:`../prog_guide/ipsec_lib` for more information. 163 164* **Updated the ipsec-secgw sample application.** 165 166 The ``ipsec-secgw`` sample application has been updated to use the new 167 ``librte_ipsec`` library, which has also been added in this release. 168 The original functionality of ipsec-secgw is retained, a new command line 169 parameter ``-l`` has been added to ipsec-secgw to use the IPsec library, 170 instead of the existing IPsec code in the application. 171 172 The IPsec library does not support all the functionality of the existing 173 ipsec-secgw application. It is planned to add the outstanding functionality 174 in future releases. 175 176 See :doc:`../sample_app_ug/ipsec_secgw` for more information. 177 178* **Enabled checksum support in the ISA-L compressdev driver.** 179 180 Added support for both adler and crc32 checksums in the ISA-L PMD. 181 This aids data integrity across both compression and decompression. 182 183* **Added a compression performance test tool.** 184 185 Added a new performance test tool to test the compressdev PMD. The tool tests 186 compression ratio and compression throughput. 187 188* **Added intel_pstate support to Power Management library.** 189 190 Previously, using the power management library required the 191 disabling of the intel_pstate kernel driver, and the enabling of the 192 acpi_cpufreq kernel driver. This is no longer the case, as the use of 193 the intel_pstate kernel driver is now supported, and automatically 194 detected by the library. 195 196 197API Changes 198----------- 199 200.. This section should contain API changes. Sample format: 201 202 * sample: Add a short 1-2 sentence description of the API change 203 which was announced in the previous releases and made in this release. 204 Start with a scope label like "ethdev:". 205 Use fixed width quotes for ``function_names`` or ``struct_names``. 206 Use the past tense. 207 208 This section is a comment. Do not overwrite or remove it. 209 Also, make sure to start the actual text at the margin. 210 ========================================================= 211 212* eal: Function ``rte_bsf64`` in ``rte_bitmap.h`` has been renamed to 213 ``rte_bsf64_safe`` and moved to ``rte_common.h``. A new ``rte_bsf64`` 214 function has been added in ``rte_common.h`` that follows the convention set 215 by the existing ``rte_bsf32`` function. 216 217* eal: Segment fd API on Linux now sets error code to ``ENOTSUP`` in more cases 218 where segment the fd API is not expected to be supported: 219 220 - On attempt to get a segment fd for an externally allocated memory segment 221 - In cases where memfd support would have been required to provide segment 222 fds (such as in-memory or no-huge mode) 223 224* eal: Functions ``rte_malloc_dump_stats()``, ``rte_malloc_dump_heaps()`` and 225 ``rte_malloc_get_socket_stats()`` are no longer safe to call concurrently with 226 ``rte_malloc_heap_create()`` or ``rte_malloc_heap_destroy()`` function calls. 227 228* mbuf: ``RTE_MBUF_INDIRECT()``, which was deprecated in 18.05, was replaced 229 with ``RTE_MBUF_CLONED()`` and removed in 19.02. 230 231* sched: As result of the new format of the mbuf sched field, the 232 functions ``rte_sched_port_pkt_write()`` and 233 ``rte_sched_port_pkt_read_tree_path()`` got an additional parameter of 234 type ``struct rte_sched_port``. 235 236* pdump: The ``rte_pdump_set_socket_dir()``, the parameter ``path`` of 237 ``rte_pdump_init()`` and enum ``rte_pdump_socktype`` were deprecated 238 since 18.05 and are removed in this release. 239 240* cryptodev: The parameter ``session_pool`` in the function 241 ``rte_cryptodev_queue_pair_setup()`` is removed. 242 243* cryptodev: a new function ``rte_cryptodev_sym_session_pool_create()`` has been 244 introduced. This function is now mandatory when creating symmetric session 245 header mempool. Please note all crypto applications are required to use this 246 function from now on. Failed to do so will cause a 247 ``rte_cryptodev_sym_session_create()`` function call return error. 248 249 250ABI Changes 251----------- 252 253.. This section should contain ABI changes. Sample format: 254 255 * sample: Add a short 1-2 sentence description of the ABI change 256 which was announced in the previous releases and made in this release. 257 Start with a scope label like "ethdev:". 258 Use fixed width quotes for ``function_names`` or ``struct_names``. 259 Use the past tense. 260 261 This section is a comment. Do not overwrite or remove it. 262 Also, make sure to start the actual text at the margin. 263 ========================================================= 264 265* mbuf: The format of the sched field of ``rte_mbuf`` has been changed 266 to include the following fields: ``queue ID``, ``traffic class``, ``color``. 267 268* cryptodev: as shown in the 18.11 deprecation notice, the structure 269 ``rte_cryptodev_qp_conf`` has added two parameters for symmetric session 270 mempool and symmetric session private data mempool. 271 272* cryptodev: as shown in the 18.11 deprecation notice, the structure 273 ``rte_cryptodev_sym_session`` has been updated to contain more information 274 to ensure safely accessing the session and session private data. 275 276* security: A new field ``uint64_t opaque_data`` has been added to 277 ``rte_security_session`` structure. That would allow upper layer to easily 278 associate/de-associate some user defined data with the security session. 279 280 281Shared Library Versions 282----------------------- 283 284.. Update any library version updated in this release 285 and prepend with a ``+`` sign, like this: 286 287 libfoo.so.1 288 + libupdated.so.2 289 libbar.so.1 290 291 This section is a comment. Do not overwrite or remove it. 292 ========================================================= 293 294The libraries prepended with a plus sign were incremented in this version. 295 296.. code-block:: diff 297 298 librte_acl.so.2 299 librte_bbdev.so.1 300 librte_bitratestats.so.2 301 librte_bpf.so.1 302 librte_bus_dpaa.so.2 303 librte_bus_fslmc.so.2 304 librte_bus_ifpga.so.2 305 librte_bus_pci.so.2 306 librte_bus_vdev.so.2 307 librte_bus_vmbus.so.2 308 librte_cfgfile.so.2 309 librte_cmdline.so.2 310 librte_compressdev.so.1 311 + librte_cryptodev.so.6 312 librte_distributor.so.1 313 librte_eal.so.9 314 librte_efd.so.1 315 librte_ethdev.so.11 316 librte_eventdev.so.6 317 librte_flow_classify.so.1 318 librte_gro.so.1 319 librte_gso.so.1 320 librte_hash.so.2 321 librte_ip_frag.so.1 322 librte_jobstats.so.1 323 librte_kni.so.2 324 librte_kvargs.so.1 325 librte_latencystats.so.1 326 librte_lpm.so.2 327 + librte_mbuf.so.5 328 librte_member.so.1 329 librte_mempool.so.5 330 librte_meter.so.2 331 librte_metrics.so.1 332 librte_net.so.1 333 librte_pci.so.1 334 + librte_pdump.so.3 335 librte_pipeline.so.3 336 librte_pmd_bnxt.so.2 337 librte_pmd_bond.so.2 338 librte_pmd_i40e.so.2 339 librte_pmd_ixgbe.so.2 340 librte_pmd_dpaa2_qdma.so.1 341 librte_pmd_ring.so.2 342 librte_pmd_softnic.so.1 343 librte_pmd_vhost.so.2 344 librte_port.so.3 345 librte_power.so.1 346 librte_rawdev.so.1 347 librte_reorder.so.1 348 librte_ring.so.2 349 + librte_sched.so.2 350 + librte_security.so.2 351 librte_table.so.3 352 librte_timer.so.1 353 librte_vhost.so.4 354 355 356Known Issues 357------------ 358 359.. This section should contain new known issues in this release. Sample format: 360 361 * **Add title in present tense with full stop.** 362 363 Add a short 1-2 sentence description of the known issue 364 in the present tense. Add information on any known workarounds. 365 366 This section is a comment. Do not overwrite or remove it. 367 Also, make sure to start the actual text at the margin. 368 ========================================================= 369 370* ``AVX-512`` support has been disabled for ``GCC`` builds when ``binutils 2.30`` 371 is detected [1] because of a crash [2]. This can affect ``native`` machine type 372 build targets on the platforms that support ``AVX512F`` like ``Intel Skylake`` 373 processors, and can cause a possible performance drop. The immediate workaround 374 is to use ``clang`` compiler on these platforms. 375 Initial workaround in DPDK v18.11 was to disable ``AVX-512`` support for ``GCC`` 376 completely, but based on information on defect submitted to GCC community [3], 377 issue has been identified as ``binutils 2.30`` issue. Since currently only GCC 378 generates ``AVX-512`` instructions, the scope is limited to ``GCC`` and 379 ``binutils 2.30`` 380 381 - [1]: Commit ("mk: fix scope of disabling AVX512F support") 382 - [2]: https://bugs.dpdk.org/show_bug.cgi?id=97 383 - [3]: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88096 384 385 386Tested Platforms 387---------------- 388 389.. This section should contain a list of platforms that were tested 390 with this release. 391 392 The format is: 393 394 * <vendor> platform with <vendor> <type of devices> combinations 395 396 * List of CPU 397 * List of OS 398 * List of devices 399 * Other relevant details... 400 401 This section is a comment. Do not overwrite or remove it. 402 Also, make sure to start the actual text at the margin. 403 ========================================================= 404 405* Intel(R) platforms with Intel(R) NICs combinations 406 407 * CPU 408 409 * Intel(R) Atom(TM) CPU C3758 @ 2.20GHz 410 * Intel(R) Xeon(R) CPU D-1541 @ 2.10GHz 411 * Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz 412 * Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 413 * Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz 414 * Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz 415 * Intel(R) Xeon(R) Gold 6139 CPU @ 2.30GHz 416 417 * OS: 418 419 * CentOS 7.4 420 * CentOS 7.5 421 * Fedora 25 422 * Fedora 28 423 * FreeBSD 11.2 424 * FreeBSD 12.0 425 * Red Hat Enterprise Linux Server release 7.4 426 * Red Hat Enterprise Linux Server release 7.5 427 * Open SUSE 15 428 * Wind River Linux 8 429 * Ubuntu 14.04 430 * Ubuntu 16.04 431 * Ubuntu 16.10 432 * Ubuntu 18.04 433 * Ubuntu 18.10 434 435 * NICs: 436 437 * Intel(R) 82599ES 10 Gigabit Ethernet Controller 438 439 * Firmware version: 0x61bf0001 440 * Device id (pf/vf): 8086:10fb / 8086:10ed 441 * Driver version: 5.2.3 (ixgbe) 442 443 * Intel(R) Corporation Ethernet Connection X552/X557-AT 10GBASE-T 444 445 * Firmware version: 0x800003e7 446 * Device id (pf/vf): 8086:15ad / 8086:15a8 447 * Driver version: 4.4.6 (ixgbe) 448 449 * Intel(R) Ethernet Converged Network Adapter X710-DA4 (4x10G) 450 451 * Firmware version: 6.80 0x80003cc1 452 * Device id (pf/vf): 8086:1572 / 8086:154c 453 * Driver version: 2.7.26 (i40e) 454 455 * Intel(R) Corporation Ethernet Connection X722 for 10GbE SFP+ (4x10G) 456 457 * Firmware version: 3.33 0x80000fd5 0.0.0 458 * Device id (pf/vf): 8086:37d0 / 8086:37cd 459 * Driver version: 2.7.26 (i40e) 460 461 * Intel(R) Ethernet Converged Network Adapter XXV710-DA2 (2x25G) 462 463 * Firmware version: 6.80 0x80003d05 464 * Device id (pf/vf): 8086:158b / 8086:154c 465 * Driver version: 2.7.26 (i40e) 466 467 * Intel(R) Ethernet Converged Network Adapter XL710-QDA2 (2X40G) 468 469 * Firmware version: 6.80 0x80003cfb 470 * Device id (pf/vf): 8086:1583 / 8086:154c 471 * Driver version: 2.7.26 (i40e) 472 473 * Intel(R) Corporation I350 Gigabit Network Connection 474 475 * Firmware version: 1.63, 0x80000dda 476 * Device id (pf/vf): 8086:1521 / 8086:1520 477 * Driver version: 5.4.0-k (igb) 478 479* Intel(R) platforms with Mellanox(R) NICs combinations 480 481 * CPU: 482 483 * Intel(R) Xeon(R) Gold 6154 CPU @ 3.00GHz 484 * Intel(R) Xeon(R) CPU E5-2697A v4 @ 2.60GHz 485 * Intel(R) Xeon(R) CPU E5-2697 v3 @ 2.60GHz 486 * Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz 487 * Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz 488 * Intel(R) Xeon(R) CPU E5-2640 @ 2.50GHz 489 * Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz 490 491 * OS: 492 493 * Red Hat Enterprise Linux Server release 7.6 (Maipo) 494 * Red Hat Enterprise Linux Server release 7.5 (Maipo) 495 * Red Hat Enterprise Linux Server release 7.4 (Maipo) 496 * Red Hat Enterprise Linux Server release 7.3 (Maipo) 497 * Red Hat Enterprise Linux Server release 7.2 (Maipo) 498 * Ubuntu 18.10 499 * Ubuntu 18.04 500 * Ubuntu 17.10 501 * Ubuntu 16.04 502 * SUSE Linux Enterprise Server 15 503 504 * MLNX_OFED: 4.4-2.0.1.0 505 * MLNX_OFED: 4.5-1.0.1.0 506 507 * NICs: 508 509 * Mellanox(R) ConnectX(R)-3 Pro 40G MCX354A-FCC_Ax (2x40G) 510 511 * Host interface: PCI Express 3.0 x8 512 * Device ID: 15b3:1007 513 * Firmware version: 2.42.5000 514 515 * Mellanox(R) ConnectX(R)-4 10G MCX4111A-XCAT (1x10G) 516 517 * Host interface: PCI Express 3.0 x8 518 * Device ID: 15b3:1013 519 * Firmware version: 12.24.1000 and above 520 521 * Mellanox(R) ConnectX(R)-4 10G MCX4121A-XCAT (2x10G) 522 523 * Host interface: PCI Express 3.0 x8 524 * Device ID: 15b3:1013 525 * Firmware version: 12.24.1000 and above 526 527 * Mellanox(R) ConnectX(R)-4 25G MCX4111A-ACAT (1x25G) 528 529 * Host interface: PCI Express 3.0 x8 530 * Device ID: 15b3:1013 531 * Firmware version: 12.24.1000 and above 532 533 * Mellanox(R) ConnectX(R)-4 25G MCX4121A-ACAT (2x25G) 534 535 * Host interface: PCI Express 3.0 x8 536 * Device ID: 15b3:1013 537 * Firmware version: 12.24.1000 and above 538 539 * Mellanox(R) ConnectX(R)-4 40G MCX4131A-BCAT/MCX413A-BCAT (1x40G) 540 541 * Host interface: PCI Express 3.0 x8 542 * Device ID: 15b3:1013 543 * Firmware version: 12.24.1000 and above 544 545 * Mellanox(R) ConnectX(R)-4 40G MCX415A-BCAT (1x40G) 546 547 * Host interface: PCI Express 3.0 x16 548 * Device ID: 15b3:1013 549 * Firmware version: 12.24.1000 and above 550 551 * Mellanox(R) ConnectX(R)-4 50G MCX4131A-GCAT/MCX413A-GCAT (1x50G) 552 553 * Host interface: PCI Express 3.0 x8 554 * Device ID: 15b3:1013 555 * Firmware version: 12.24.1000 and above 556 557 * Mellanox(R) ConnectX(R)-4 50G MCX414A-BCAT (2x50G) 558 559 * Host interface: PCI Express 3.0 x8 560 * Device ID: 15b3:1013 561 * Firmware version: 12.24.1000 and above 562 563 * Mellanox(R) ConnectX(R)-4 50G MCX415A-GCAT/MCX416A-BCAT/MCX416A-GCAT (2x50G) 564 565 * Host interface: PCI Express 3.0 x16 566 * Device ID: 15b3:1013 567 * Firmware version: 12.24.1000 and above 568 * Firmware version: 12.24.1000 and above 569 570 * Mellanox(R) ConnectX(R)-4 50G MCX415A-CCAT (1x100G) 571 572 * Host interface: PCI Express 3.0 x16 573 * Device ID: 15b3:1013 574 * Firmware version: 12.24.1000 and above 575 576 * Mellanox(R) ConnectX(R)-4 100G MCX416A-CCAT (2x100G) 577 578 * Host interface: PCI Express 3.0 x16 579 * Device ID: 15b3:1013 580 * Firmware version: 12.24.1000 and above 581 582 * Mellanox(R) ConnectX(R)-4 Lx 10G MCX4121A-XCAT (2x10G) 583 584 * Host interface: PCI Express 3.0 x8 585 * Device ID: 15b3:1015 586 * Firmware version: 14.24.1000 and above 587 588 * Mellanox(R) ConnectX(R)-4 Lx 25G MCX4121A-ACAT (2x25G) 589 590 * Host interface: PCI Express 3.0 x8 591 * Device ID: 15b3:1015 592 * Firmware version: 14.24.1000 and above 593 594 * Mellanox(R) ConnectX(R)-5 100G MCX556A-ECAT (2x100G) 595 596 * Host interface: PCI Express 3.0 x16 597 * Device ID: 15b3:1017 598 * Firmware version: 16.24.1000 and above 599 600 * Mellanox(R) ConnectX(R)-5 Ex EN 100G MCX516A-CDAT (2x100G) 601 602 * Host interface: PCI Express 4.0 x16 603 * Device ID: 15b3:1019 604 * Firmware version: 16.24.1000 and above 605 606* ARM platforms with Mellanox(R) NICs combinations 607 608 * CPU: 609 610 * Qualcomm ARM 1.1 2500MHz 611 612 * OS: 613 614 * Red Hat Enterprise Linux Server release 7.5 (Maipo) 615 616 * NICs: 617 618 * Mellanox(R) ConnectX(R)-4 Lx 25G MCX4121A-ACAT (2x25G) 619 620 * Host interface: PCI Express 3.0 x8 621 * Device ID: 15b3:1015 622 * Firmware version: 14.24.0220 623 624 * Mellanox(R) ConnectX(R)-5 100G MCX556A-ECAT (2x100G) 625 626 * Host interface: PCI Express 3.0 x16 627 * Device ID: 15b3:1017 628 * Firmware version: 16.24.0220 629 630* Mellanox(R) BlueField SmartNIC 631 632 * Mellanox(R) BlueField SmartNIC MT416842 (2x25G) 633 634 * Host interface: PCI Express 3.0 x16 635 * Device ID: 15b3:a2d2 636 * Firmware version: 18.24.0328 637 638 * SoC ARM cores running OS: 639 640 * CentOS Linux release 7.4.1708 (AltArch) 641 * MLNX_OFED 4.4-2.5.9.0 642 643 * DPDK application running on ARM cores inside SmartNIC 644 645* Power 9 platforms with Mellanox(R) NICs combinations 646 647 * CPU: 648 649 * POWER9 2.2 (pvr 004e 1202) 2300MHz 650 651 * OS: 652 653 * Ubuntu 18.04.1 LTS (Bionic Beaver) 654 655 * NICs: 656 657 * Mellanox(R) ConnectX(R)-5 100G MCX556A-ECAT (2x100G) 658 659 * Host interface: PCI Express 3.0 x16 660 * Device ID: 15b3:1017 661 * Firmware version: 16.23.1020 662 663 * OFED: 664 665 * MLNX_OFED_LINUX-4.5-1.0.1.0 666