NVIDIA 699210040230 DPU Firmware 24.40.1000

Firmware which is added at the time of manufacturing, is used to run user programs on the device and can be thought of as the software that allows hardware to run. Embedded firmware is used to control the functions of various hardware devices and systems, much like a computer’s operating system (OS) controls the function of software applications. Firmware may be written into read-only memory (ROM), erasable programmable read-only memory (EPROM) or flash memory.

NVIDIA BlueField-2 DPU provides innovative acceleration, security, and efficiency in every host. BlueField-2 data center infrastructure combines the power of the NVIDIA ConnectX-6 Dx with programmable Arm cores and hardware offloads for software-defined storage, networking, security, and management workloads.

NVIDIA BlueField-2 also delivers superior performance, security, and reduced TCO for cloud computing platforms, enabling organizations to efficiently build and operate virtualized, containerized, and bare-metal infrastructures at massive scale.

Changes and New Features:

- Enabled Single Netdev mapping to two PCIe devices (Socket Direct). Now multiple devices (PFs) of the same port can be combined under a single netdev instance. Traffic is passed through different devices belonging to different NUMA sockets, thus saving cross-NUMA traffic and allowing apps running on the same netdev from different NUMAs to still feel a sense of proximity to the device and achieve improved performance. The netdev is destroyed once any of the PFs is removed. A proper configuration would utilize the correct close NUMA when working on a certain app/CPU. Currently, this capability is limited to PFs only, and up to two devices (sockets). To enable the feature, one must configure the same Socket Direct group (non zero) for both PFs through mlxconfig SD_GROUP.
- Added support for egress ACL to the uplink by adding a new bit to the Set Flow Table Entry: allow_fdb_uplink_hairpin.

Bug Fixes:

 
- Changed HW ETS (QETCR RL) default to be per host-port instead of per physical port to avoid bandwidth degradation.
- Fixed an issue that resulted in DESTROY_GENERAL_OBJECT(0xa03) and MODIFY_GENERAL_OBJECT(0xa01) getting timeout when performing a host power cycle with an independent-power-supplied BlueField-2 on which the virtio devices are hotplugged.
- Fixed an issue with Selective-Repeat configuration which occasionally caused retransmission to wait for timeout instead of out-of-sequence NACK.
- Enabled the lowest minimum rate for SW DCQCN to enable congestion control to hold a larger amount of QPs without pauses or drops.
- Redirected multicast traffic to loopback only on MNG PF port using PT Tx loopback CAM HW mechanism.
- Fixed the cr_space in port configuration to prevent wrong timestamp of cqes.
- Fixed an issue that resulted in reset failure when unloading network drivers on an external host and the sync1 reset is still reported as 'supported' although it is not.
- Fixed an issue that prevented the Power Controller Control bit in the Slot Control register from returning to default when forcing the Unplug sequence.
- Added a locking mechanism to protect the firmware from a race condition between insertion and deletion of the same rule in parallel which occasionally resulted in firmware accessing a memory that has already been released, thus causing IOMMU / translation error.
- Enabled live migration for virtio with mergeable buffer.
- Fixed an issue that resulted in migration data corruption when running parallel save_vhca_state/load_vhca_state commands on the same PF.

Known Issues:

- PHYless Reset is currently not supported.
- Some pre-OS environments may fail when sensing a hot-plug operation during their boot stage.
- Unexpected system behavior might be observed if the driver is loaded while reset is in progress.
- When tx_port_ts is set to "true", due to a compensation mechanism in the Tx timestamp available in some hardware Rx timestamp errors, a symmetrical error and no clock offset occur when using the timestamps to synchronize the device clock. This might also cause an error while using timestamps for delay measurements (e,g., delay measurements reported by a PTP daemon) and even negative delay measurements in some cases.
- When unloading the network drivers on an external host, sync1 reset may be still reported as 'supported' although it is not. Thus, initiating the reset flow may result in reset failure after a few minutes.
- Disabling the Relaxed Ordered (RO) capability (relaxed_ordering_read_pci_enabled=0) using the vhca_resource_manager is currently not functional.
- fwreset is currently supported on PCI Gen 4 devices only.
- The firmware rollback fails for the signature retransmit flow if the QPN field is configured in the mkey (as it only allows the given QP to use this Mkey) as the firmware rollback flow relies on an internal QP that uses the mkey.
- MFS1S50-H003E cable supports only HDR rate when used as a split cable.
- CRC is included in the traffic byte counters as a port byte counter.
- The "max_shaper_rate" configuration query via QEEC mlxreg returns a value translated to hardware granularity.
- GTP encapsulation (flex parser profile 3) is limited to the NIC domain. Encapsulating in the FDB domain will render a 0-size length in GTP header.
- Some pre-OS environments may fail when sensing a hot plug operation during their boot stage.
- Servers do not recover after configuring PCI_SWITCH_EMULATION_NUM_PORT to 32 followed by power cycle.
- When working with 3rd party device (e.g., Paragon) in 25GbE speed, the 25GbE speed must be configured in force mode.
- Occasionally, when rising a logical link, the link recovery counter is increase by 1.
- Forward action for IPoIB is not supported on RX RDMA Flow Table.

About Network Adapter Drivers:

When connected, the operating system usually installs a generic driver that helps the computer to recognize the newly attached device.

However, proper software must be applied if you want to make use of all features that the network adapter has available. This task also allows computers to properly recognize all device characteristics such as manufacturer, chipset, technology, and others.

Updating the adapter's drivers and utilities version might improve overall performance and stability, increase transfer speeds, fix different compatibility problems and several network-related errors, as well as bring various other changes.

To install this release, simply get the package, extract it if necessary, run the setup, and follow the instructions displayed on-screen. When done, don't forget to perform a system restart and reconnect the network adapter to make sure that all changes take effect properly.

Without further ado, if you intend to apply this version, click the download button and install the package. Moreover, check with our website as often as possible so that you don't miss a single new release.