patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <luca.boccassi@gmail.com>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: stable@dpdk.org, dev@dpdk.org,
	John McNamara <john.mcnamara@intel.com>,
	 Raslan Darawsheh <rasland@nvidia.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	sbadawi@nvidia.com, waela@nvidia.com
Subject: Re: 22.11.11 patches review and test
Date: Mon, 22 Dec 2025 11:26:52 +0000	[thread overview]
Message-ID: <CAMw=ZnRPba=cPc1waWhmzkkSK_+iKpdhuFf8u9QZZqDjmScUYA@mail.gmail.com> (raw)
In-Reply-To: <CAMw=ZnQwf8cH_cO9CK3Y--XmzYU+cfCNJ3YWe8qjNZbuCfSe6Q@mail.gmail.com>

On Thu, 18 Dec 2025 at 19:06, Luca Boccassi <luca.boccassi@gmail.com> wrote:
>
> On Thu, 18 Dec 2025 at 18:58, Ali Alnubani <alialnu@nvidia.com> wrote:
> >
> >
> > On 12/18/25 8:27 PM, Luca Boccassi wrote:
> > > 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?
> >
> > I reached out to the engineer who authored the patch and am waiting for
> > their response. I may not be able to get back to you with an answer
> > today, though.
>
> Thank you, no problem it can wait a while

Hi,

Any update?

Thanks

      reply	other threads:[~2025-12-22 11:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04  0:56 luca.boccassi
2025-12-08  8:03 ` Yanghang Liu
2025-12-08 10:28   ` Luca Boccassi
2025-12-12  6:51 ` Xu, HailinX
2025-12-12  6:53 ` Xu, HailinX
2025-12-12 12:25   ` Luca Boccassi
2025-12-18 18:23 ` Ali Alnubani
2025-12-18 18:27   ` Luca Boccassi
2025-12-18 18:58     ` Ali Alnubani
2025-12-18 19:06       ` Luca Boccassi
2025-12-22 11:26         ` 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=ZnRPba=cPc1waWhmzkkSK_+iKpdhuFf8u9QZZqDjmScUYA@mail.gmail.com' \
    --to=luca.boccassi@gmail.com \
    --cc=alialnu@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=rasland@nvidia.com \
    --cc=sbadawi@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=waela@nvidia.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;
as well as URLs for NNTP newsgroup(s).