DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Ali Alnubani <alialnu@nvidia.com>, stable@dpdk.org
Cc: dev@dpdk.org, John McNamara <john.mcnamara@intel.com>,
	Ju-Hyoung Lee <juhlee@microsoft.com>,
	Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
	Raslan Darawsheh <rasland@nvidia.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: 24.11.3 patches review and test
Date: Thu, 14 Aug 2025 11:27:40 +0100	[thread overview]
Message-ID: <2f601b6c-6316-40cc-9b86-31af16017258@redhat.com> (raw)
In-Reply-To: <1a0cca7f-fd45-433e-bc37-2b4b8ea7faee@nvidia.com>

On 13/08/2025 21:25, Ali Alnubani wrote:
> On 7/24/25 7:15 PM, Kevin Traynor wrote:
> 
>> Hi all,
>>
>> Here is a list of patches targeted for stable release 24.11.3.
>>
>> The planned date for the final release is 12th August 2025.
>>
>> Please help with testing and validation of your use cases and report
>> any issues/results with reply-all to this mail. For the final release
>> the fixes and reported validations will be added to the release notes.
>>
>> A release candidate tarball can be found at:
>>
>>      https://dpdk.org/browse/dpdk-stable/tag/?id=v24.11.3-rc1
>>
>> These patches are located at branch 24.11 of dpdk-stable repo:
>>      https://dpdk.org/browse/dpdk-stable/
>>
>> Thanks.
>>
>> Kevin
>>
>> ---
> 
> Hello Kevin, apologies for the delay,
> 

Hi Ali,

No problem, thanks for taking the time to run the validation.

> We ran the following functional tests with Nvidia hardware on v24.11.3-rc1:
> - Basic functionality:
>    Send and receive multiple types of traffic.
> - testpmd xstats counter test.
> - testpmd timestamp test.
> - Changing/checking link status through testpmd.
> - rte_flow tests 
> (https://doc.dpdk.org/guides/nics/mlx5.html#supported-hardware-offloads)
> - RSS tests.
> - VLAN filtering, stripping, and insertion tests.
> - Checksum and TSO tests.
> - ptype tests.
> - link_status_interrupt example application tests.
> - l3fwd-power example application tests.
> - Multi-process example applications tests.
> - Hardware LRO tests.
> - Buffer Split tests.
> - Tx scheduling tests.
> 
> Functional tests ran on:
> - NIC: ConnectX-6 Dx / OS: Ubuntu 22.04 / Driver: 
> MLNX_OFED_LINUX-24.10-3.2.5.0 / Firmware: 22.43.3608
> - NIC: ConnectX-7 / OS: Ubuntu 22.04 / Driver: 
> MLNX_OFED_LINUX-24.10-3.2.5.0 / Firmware: 28.43.3608
> - DPU: BlueField-2 / DOCA SW version: 2.9.3 / Firmware: 24.43.3608
> 
> Additionally, we ran build tests with multiple configurations on the 
> following OS/driver combinations (all passed):
> - Debian 12 with MLNX_OFED_LINUX-24.10-3.2.5.0.
> - Ubuntu 22.04 with MLNX_OFED_LINUX-24.10-3.2.5.0.
> - Ubuntu 22.04 with rdma-core master (091ddb5).
> - Ubuntu 24.04 with MLNX_OFED_LINUX-24.10-3.2.5.0.
> - Ubuntu 24.04 with rdma-core v50.0.
> - Fedora 42 with rdma-core v55.0.
> - Fedora 43 (Rawhide) with rdma-core v58.0.
> - OpenSUSE Leap 15.6 with rdma-core v49.1.
> - Windows Server 2022 with Clang 18.1.8.
> 
> The following patch addresses an ASan issue in testpmd:
> https://inbox.dpdk.org/dev/20250730113243.197386-1-mkashani@nvidia.com/
> 

ok, that one is not merged in dpdk main branch or gone through release
validation yet, so will hold off applying into stable branch for now.

> We are currently investigating additional functional test failures but 
> have not yet determined if these issues are new or present in previous 
> releases (and appeared due to environment changes). Will update as soon 
> as possible.
> 

Sure, no problem.

thanks,
Kevin.

> Regards,
> Ali
> 


  reply	other threads:[~2025-08-14 10:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24 16:15 Kevin Traynor
2025-07-28  9:14 ` Yanghang Liu
2025-07-28 10:09   ` Kevin Traynor
2025-08-13 20:25 ` Ali Alnubani
2025-08-14 10:27   ` Kevin Traynor [this message]
2025-08-14  6:01 ` Xu, HailinX
2025-08-14 10:02   ` Kevin Traynor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2f601b6c-6316-40cc-9b86-31af16017258@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=alialnu@nvidia.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=juhlee@microsoft.com \
    --cc=pezhang@redhat.com \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).