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" <stable@dpdk.org>,
	"dev@dpdk.org" <dev@dpdk.org>,
	 John McNamara <john.mcnamara@intel.com>,
	Raslan Darawsheh <rasland@nvidia.com>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
	Wael Abualrub <waela@nvidia.com>
Subject: Re: 20.11.9 patches review and test
Date: Mon, 14 Aug 2023 12:55:18 +0100	[thread overview]
Message-ID: <CAMw=ZnS7G2ETgXSg=KK9=oGkmkHmLRERASPgfY_ZzmvTj12+Rw@mail.gmail.com> (raw)
In-Reply-To: <DM4PR12MB5167A8700372876016C87D14DA17A@DM4PR12MB5167.namprd12.prod.outlook.com>

On Mon, 14 Aug 2023 at 12:52, Ali Alnubani <alialnu@nvidia.com> wrote:
>
> > -----Original Message-----
> > From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> > Sent: Saturday, July 29, 2023 2:08 AM
> > To: stable@dpdk.org
> > Cc: dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.com>;
> > Ali Alnubani <alialnu@nvidia.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>;
> > Pei Zhang <pezhang@redhat.com>; qian.q.xu@intel.com; Raslan Darawsheh
> > <rasland@nvidia.com>; NBU-Contact-Thomas Monjalon (EXTERNAL)
> > <thomas@monjalon.net>; Yanghang Liu <yanghliu@redhat.com>;
> > yuan.peng@intel.com; zhaoyan.chen@intel.com
> > Subject: 20.11.9 patches review and test
> >
> > Hi all,
> >
> > Here is a list of patches targeted for stable release 20.11.9.
> >
> > The planned date for the final release is the 14th of August 2023.
> >
> > 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=v20.11.9-rc1
> >
> > These patches are located at branch 20.11 of dpdk-stable repo:
> >     https://dpdk.org/browse/dpdk-stable/
> >
> > Thanks.
> >
> > Luca Boccassi
> >
> > ---
>
>  Hello,
>
> Apologies for the last-minute reply.
>
> We ran the following functional tests with Nvidia hardware on v20.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.
> - Some 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.
>
> Functional tests ran on these cards:
> - NIC: ConnectX-6 Dx / OS: Ubuntu 20.04 / Driver: MLNX_OFED_LINUX-23.04-1.1.3.0 / Firmware: 22.37.1014
> - NIC: ConnectX-7 / OS: Ubuntu 20.04 / Driver: MLNX_OFED_LINUX-23.04-1.1.3.0 / Firmware: 28.37.1014
> - DPU: BlueField-2 / DOCA SW version: 2.0.2 / Firmware: 24.37.1300
>
> Build tests (all passed):
> - Ubuntu 20.04.6 with MLNX_OFED_LINUX-23.04-1.1.3.0.
> - Ubuntu 20.04.6 with rdma-core master (aba30bd).
> - Ubuntu 20.04.6 with rdma-core v28.0.
> - Ubuntu 18.04.6 with rdma-core master (aba30bd) (i386).
> - Fedora 38 with rdma-core v44.0.
> - Fedora 39 (Rawhide) with rdma-core v46.0.
> - OpenSUSE Leap 15.5 with rdma-core v42.0.
> - Windows Server 2019 with Clang 11.0.0.
>
> We see warnings while restarting ports in testpmd application if MPRQ is enabled, and we think it's caused by this backported change:
> net/mlx5: fix MPRQ stride size to accommodate the headroom (https://git.dpdk.org/dpdk-stable/commit/?h=81002988e01)
> This is the only issue we found that might've been caused by changes in this release. Hope I can update by tomorrow.
>
> We're investigating some internal test failures that were caused by environment changes, but we have a high pass rate in our regression testing overall.
>
> Thanks,
> Ali

Thank you, I'll wait for the conclusion on that, if I need to revert
that change let me know.

Kind regards,
Luca Boccassi

  reply	other threads:[~2023-08-14 11:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28 23:07 luca.boccassi
2023-08-07  7:41 ` Xu, HailinX
2023-08-07  9:18   ` Luca Boccassi
2023-08-11  3:06 ` YangHang Liu
2023-08-11  8:21   ` Luca Boccassi
2023-08-14 11:52 ` Ali Alnubani
2023-08-14 11:55   ` Luca Boccassi [this message]
2023-08-15 13:35     ` Ali Alnubani
2023-08-15 15:03       ` Luca Boccassi

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=ZnS7G2ETgXSg=KK9=oGkmkHmLRERASPgfY_ZzmvTj12+Rw@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=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).