Re: 22.11.11 patches review and test

[Luca Boccassi <luca.boccassi@gmail.com>]

On Thu, 18 Dec 2025 at 18:24, Ali Alnubani <alialnu@nvidia.com> wrote:
>
> On 12/4/25 2:56 AM, luca.boccassi@gmail.com wrote:
>
> > Hi all,
> >
> > Here is a list of patches targeted for stable release 22.11.11.
> >
> > The planned date for the final release is December 18th.
> >
> > 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.11-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.11-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 ConnectX-6 Dx (OS: Ubuntu 22.04 | Driver:
> MLNX_OFED_LINUX-5.8-7.0.6.1 | Firmware: 22.35.8002).
>
> An engineer from my team reported 2 issues:
>
> https://bugs.dpdk.org/show_bug.cgi?id=1851
> Did not reproduce in 22.11.10, git-bisect points to 58a6421bc396
> ("net/mlx5: fix multicast")..

Thanks, are you planning to send a fix, or should I just revert that commit?

> https://bugs.dpdk.org/show_bug.cgi?id=1852
> Reproduces on v22.11.10.

Given it's not new, unless someone can send a patch to fix it, I'll
leave it as-is