<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi Ali,</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks for your support, will collection into release notes.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Regarding the gcc 15 warnning, it's a small issue, I will fix it in the next release.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Best regards,</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Xueming</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Ali Alnubani <alialnu@nvidia.com><br>
<b>Sent:</b> Friday, April 25, 2025 3:30 AM<br>
<b>To:</b> Xueming Li <xuemingl@nvidia.com>; stable@dpdk.org <stable@dpdk.org><br>
<b>Cc:</b> dev@dpdk.org <dev@dpdk.org>; Abhishek Marathe <Abhishek.Marathe@microsoft.com>; David Christensen <drc@linux.vnet.ibm.com>; Hemant Agrawal <hemant.agrawal@nxp.com>; Ian Stokes <ian.stokes@intel.com>; Jerin Jacob <jerinj@marvell.com>; John McNamara
<john.mcnamara@intel.com>; Ju-Hyoung Lee <juhlee@microsoft.com>; Kevin Traynor <ktraynor@redhat.com>; Luca Boccassi <bluca@debian.org>; Pei Zhang <pezhang@redhat.com>; Raslan Darawsheh <rasland@nvidia.com>; NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>;
Yanghang Liu <yanghliu@redhat.com>; benjamin.walker@intel.com <benjamin.walker@intel.com>; qian.q.xu@intel.com <qian.q.xu@intel.com>; yuan.peng@intel.com <yuan.peng@intel.com>; zhaoyan.chen@intel.com <zhaoyan.chen@intel.com><br>
<b>Subject:</b> Re: 23.11.4 patches review and test</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">On 4/21/25 5:19 PM, Xueming Li wrote:<br>
<br>
> Hi all,<br>
><br>
> Here is a list of patches targeted for stable release 23.11.4.<br>
><br>
> The planned date for the final release is 25th April.<br>
><br>
> Please help with testing and validation of your use cases and report<br>
> any issues/results with reply-all to this mail. For the final release<br>
> the fixes and reported validations will be added to the release notes.<br>
><br>
> A release candidate tarball can be found at:<br>
><br>
> <a href="https://dpdk.org/browse/dpdk-stable/tag/?id=v23.11.4-rc4">https://dpdk.org/browse/dpdk-stable/tag/?id=v23.11.4-rc4</a><br>
><br>
> These patches are located at branch 23.11 of dpdk-stable repo:<br>
> <a href="https://dpdk.org/browse/dpdk-stable/">https://dpdk.org/browse/dpdk-stable/</a><br>
><br>
> Thanks.<br>
><br>
> Xueming Li <xuemingl@nvidia.com><br>
><br>
> ---<br>
<br>
Hello,<br>
<br>
We ran the following functional tests with Nvidia hardware on v23.11.4-rc4:<br>
- Basic functionality:<br>
Send and receive multiple types of traffic.<br>
- testpmd xstats counter test.<br>
- testpmd timestamp test.<br>
- Changing/checking link status through testpmd.<br>
- rte_flow tests <br>
(<a href="https://doc.dpdk.org/guides/nics/mlx5.html#supported-hardware-offloads">https://doc.dpdk.org/guides/nics/mlx5.html#supported-hardware-offloads</a>)<br>
- RSS tests.<br>
- VLAN filtering, stripping, and insertion tests.<br>
- Checksum and TSO tests.<br>
- ptype tests.<br>
- link_status_interrupt example application tests.<br>
- l3fwd-power example application tests.<br>
- Multi-process example applications tests.<br>
- Hardware LRO tests.<br>
- Buffer Split tests.<br>
- Tx scheduling tests.<br>
<br>
Functional tests ran on:<br>
- NIC: ConnectX-6 Dx / OS: Ubuntu 22.04 / Driver: <br>
MLNX_OFED_LINUX-24.10-2.1.8.0 / Firmware: 22.43.2566<br>
- DPU: BlueField-2 / DOCA SW version: 2.10.0 / Firmware: 24.44.1036<br>
<br>
We saw functional test failures caused by environment changes, but <br>
didn't find issues caused by changes in this release candidate.<br>
<br>
Additionally, we ran build tests with multiple configurations on the <br>
following OS/driver combinations:<br>
- Ubuntu 22.04 with MLNX_OFED_LINUX-24.10-2.1.8.0.<br>
- Ubuntu 24.04 with MLNX_OFED_LINUX-24.10-2.1.8.0.<br>
- Ubuntu 22.04 with rdma-core master (324c42e).<br>
- Ubuntu 24.04 with rdma-core v50.0.<br>
- Fedora 41 with rdma-core v51.0.<br>
- Fedora 43 (Rawhide) with rdma-core v56.0.<br>
- OpenSUSE Leap 15.6 with rdma-core v49.1.<br>
- Windows Server 2022 with Clang 16.0.6.<br>
<br>
All build tests passed except for gcc 15.0.1 on Fedora 43, which failed <br>
with:<br>
<br>
lib/ethdev/rte_flow.h:886:36: error: initializer-string for array of <br>
'unsigned char' is too long [-Werror=unterminated-string-initialization]<br>
<br>
Thanks,<br>
Ali<br>
<br>
</div>
</span></font></div>
</body>
</html>