From: Luca Boccassi <luca.boccassi@gmail.com>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: stable@dpdk.org, dev@dpdk.org,
Raslan Darawsheh <rasland@nvidia.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: 22.11.9 patches review and test
Date: Tue, 19 Aug 2025 17:59:03 +0100 [thread overview]
Message-ID: <CAMw=ZnROFOSiejmGbndtnZ78yAJpDOOSWDrFt-S8JjzPecDogA@mail.gmail.com> (raw)
In-Reply-To: <ac197013-cec0-41cd-ac6e-0755e7dbc806@nvidia.com>
On Tue, 19 Aug 2025 at 16:32, Ali Alnubani <alialnu@nvidia.com> wrote:
>
> On 7/23/25 7:08 PM, luca.boccassi@gmail.com wrote:
>
> > Hi all,
> >
> > Here is a list of patches targeted for stable release 22.11.9.
> >
> > The planned date for the final release is by the 25th of 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=v22.11.9-rc1
> >
> > These patches are located at branch 22.11 of dpdk-stable repo:
> > https://dpdk.org/browse/dpdk-stable/
> >
> > Thanks.
> >
> > Luca Boccassi
> >
> > ---
>
> Hello,
>
> We ran the following functional tests with Nvidia hardware on v22.11.9-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-2.1.8.0 / Firmware: 22.43.2566
> - NIC: ConnectX-7 / OS: Ubuntu 22.04 / Driver:
> MLNX_OFED_LINUX-24.10-2.1.8.0 / Firmware: 28.43.2566
> - DPU: BlueField-2 / DOCA SW version: 2.5.4 / Firmware: 24.39.5050
>
> 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 24.04 with MLNX_OFED_LINUX-24.10-3.2.5.0.
> - Ubuntu 22.04 with rdma-core master (091ddb5).
> - 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.
>
> We did not detect new issues caused by changes in this release.
>
> Thanks,
> Ali
That's great, thank you
prev parent reply other threads:[~2025-08-19 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 16:08 luca.boccassi
2025-07-28 9:17 ` Yanghang Liu
2025-07-28 9:28 ` Luca Boccassi
2025-08-05 9:28 ` Xu, HailinX
2025-08-05 9:37 ` Luca Boccassi
2025-08-18 11:05 ` Luca Boccassi
2025-08-19 15:32 ` Ali Alnubani
2025-08-19 16:59 ` Luca Boccassi [this message]
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='CAMw=ZnROFOSiejmGbndtnZ78yAJpDOOSWDrFt-S8JjzPecDogA@mail.gmail.com' \
--to=luca.boccassi@gmail.com \
--cc=alialnu@nvidia.com \
--cc=dev@dpdk.org \
--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).