DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@nvidia.com>
To: Kevin Traynor <ktraynor@redhat.com>, stable@dpdk.org
Cc: dev@dpdk.org, Abhishek Marathe <Abhishek.Marathe@microsoft.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>,
	Raslan Darawsheh <rasland@nvidia.com>,
	Shani Peretz <shperetz@nvidia.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: 25.11.3 patches review and test
Date: Tue, 18 Aug 2026 18:14:22 +0300	[thread overview]
Message-ID: <45705b36-123e-4459-9287-935485b3658e@nvidia.com> (raw)
In-Reply-To: <20260804104755.135019-1-ktraynor@redhat.com>

On 8/4/26 1:47 PM, Kevin Traynor wrote:

> Hi all,
>
> Here is a list of patches targeted for stable release 25.11.3.
>
> The planned date for the final release is 20th August.
>
> 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.3-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 on v25.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 (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.

Environments:
- NIC: ConnectX-7 / OS: Ubuntu 24.04 / Driver: DOCA-Host 3.4.0-085000 / 
Firmware: 28.49.1014
- DPU: BlueField-3 / OS: Ubuntu 24.04 | DOCA SW version: 3.4.0 / 
Firmware: 24.49.1014

We don't see new issues caused by changes in this release.

Thanks,
Ali


  parent reply	other threads:[~2026-08-18 15:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 10:47 25.11.3 patches review and test Kevin Traynor
2026-08-05 10:33 ` Kevin Traynor
2026-08-18 15:14 ` Ali Alnubani [this message]
2026-08-18 15:23   ` Kevin Traynor
2026-08-20  5:47 ` Xu, HailinX
2026-08-20  9:06   ` Kevin Traynor
  -- strict thread matches above, loose matches on Subject: below --
2026-08-06  9:38 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=45705b36-123e-4459-9287-935485b3658e@nvidia.com \
    --to=alialnu@nvidia.com \
    --cc=Abhishek.Marathe@microsoft.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=ktraynor@redhat.com \
    --cc=rasland@nvidia.com \
    --cc=shperetz@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