DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@nvidia.com>
To: Shani Peretz <shperetz@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>,
	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>,
	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
Subject: Re: 23.11.7 patches review and test
Date: Wed, 29 Apr 2026 20:57:41 +0300	[thread overview]
Message-ID: <c7db1005-ef22-4e54-a09d-474d6cee77b6@nvidia.com> (raw)
In-Reply-To: <20260421064637.2506152-1-shperetz@nvidia.com>

On 4/21/26 9:46 AM, Shani Peretz wrote:

> Hi all,
>
> Here is a list of patches targeted for stable release 23.11.7.
>
> The planned date for the final release is 30 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=v23.11.7-rc1
>
> These patches are located at branch 23.11 of dpdk-stable repo:
>      https://dpdk.org/browse/dpdk-stable/
>
> Thanks.
>
> Shani
>
> ---
Hello,

We ran the following functional tests with Nvidia hardware on v23.11.7-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.

Testing environments:
- NIC: ConnectX-6 Dx / OS: Ubuntu 22.04 / Driver: 
MLNX_OFED_LINUX-23.10-6.1.6.1 / Firmware: 22.39.5124
- NIC: ConnectX-7 / OS: Ubuntu 22.04 / Driver: 
MLNX_OFED_LINUX-23.10-6.1.6.1 / Firmware: 28.39.5124
- DPU: BlueField-2 / DOCA SW version: 2.5.5 / Firmware: 24.39.5124

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

Thanks,
Ali

  reply	other threads:[~2026-04-29 17:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21  6:46 23.11.7 patches review and test Shani Peretz
2026-04-29 17:57 ` Ali Alnubani [this message]
2026-05-05 16:05   ` Shani Peretz
2026-04-30  1:29 ` Xu, HailinX
2026-05-05 16:05   ` Shani Peretz
2026-04-30  9:32 ` Kevin Traynor
2026-04-30  9:58   ` Thomas Monjalon
2026-04-30 10:02     ` Kevin Traynor
2026-05-15 10:31       ` Kevin Traynor
2026-05-15 12:36         ` Luca Boccassi
2026-05-15 16:03           ` 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=c7db1005-ef22-4e54-a09d-474d6cee77b6@nvidia.com \
    --to=alialnu@nvidia.com \
    --cc=Abhishek.Marathe@microsoft.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=ian.stokes@intel.com \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=juhlee@microsoft.com \
    --cc=ktraynor@redhat.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