DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Ali Alnubani <alialnu@nvidia.com>, stable@dpdk.org
Cc: dev@dpdk.org, Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
	benjamin.walker@intel.com,
	David Christensen <drc@linux.vnet.ibm.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Jerin Jacob <jerinj@marvell.com>,
	John McNamara <john.mcnamara@intel.com>,
	Ju-Hyoung Lee <juhlee@microsoft.com>,
	Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
	qian.q.xu@intel.com, Raslan Darawsheh <rasland@nvidia.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Yanghang Liu <yanghliu@redhat.com>,
	yuan.peng@intel.com, zhaoyan.chen@intel.com,
	Shani Peretz <shperetz@nvidia.com>
Subject: Re: 25.11.1 patches review and test
Date: Tue, 21 Apr 2026 11:13:46 +0100	[thread overview]
Message-ID: <e3b57004-9f21-480f-97f2-13c305e25547@redhat.com> (raw)
In-Reply-To: <9beb13d5-8072-4b34-8db9-2c472d6d6803@nvidia.com>

On 4/20/26 8:37 PM, Ali Alnubani wrote:
> 
> On 4/2/26 7:44 PM, Kevin Traynor wrote:
>> Hi all,
>>
>> Here is a list of patches targeted for stable release 25.11.1.
>>
>> The planned date for the final release is 21st April 2026.
>>
>> 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=v25.11.1-rc1
>>
>> These patches are located at branch 25.11 of dpdk-stable repo:
>>      https://dpdk.org/browse/dpdk-stable/
>>
>> Thanks.
>>
>> Kevin
>>
>> ---
> 
> Hello,
> 
> We ran the following functional tests with Nvidia hardware:
> 
> - 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 (See https://doc.dpdk.org/guides/nics/mlx5.html for 
> supported features)
> - 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.
> 
> We ran our testing with Shani's backport for 9ec0c6bda04a ("net/mlx5: 
> add RSS TIR registration API") on top of  v25.11.1-rc1. Environments:
> - NIC: ConnectX-7 / OS: Ubuntu 24.04 / Driver: DOCA-Host 3.3.0-088000 / 
> Firmware: 28.48.1000
> - DPU: BlueField-3 / OS: Ubuntu 24.04 | DOCA SW version: 3.3.0 / 
> Firmware: 24.48.1000
> 
> We have not identified any new issues caused by changes in this release; 
> however, we are still investigating test failures that are suspected to 
> be related to environment changes.
> 

Thanks for testing Ali. I don't mind waiting a few more days for the
release if you want some time to investigate this ? or if you are fairly
confident it is environment changes, I can go ahead with the release.

Let me know which you prefer.

thanks,
Kevin.

> Thanks,
> Ali
> 


  reply	other threads:[~2026-04-21 10:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02 16:44 25.11.1 patches review and test Kevin Traynor
2026-04-20 19:37 ` Ali Alnubani
2026-04-21 10:13   ` Kevin Traynor [this message]
2026-04-21 12:24     ` Ali Alnubani
2026-04-21  1:44 ` Xu, HailinX
2026-04-21 10:01   ` Kevin Traynor
2026-04-21  5:47 ` Riley Fletcher
2026-04-21 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=e3b57004-9f21-480f-97f2-13c305e25547@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=Abhishek.Marathe@microsoft.com \
    --cc=alialnu@nvidia.com \
    --cc=benjamin.walker@intel.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=juhlee@microsoft.com \
    --cc=pezhang@redhat.com \
    --cc=qian.q.xu@intel.com \
    --cc=rasland@nvidia.com \
    --cc=shperetz@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=yanghliu@redhat.com \
    --cc=yuan.peng@intel.com \
    --cc=zhaoyan.chen@intel.com \
    /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