From: Ali Alnubani <alialnu@oss.nvidia.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
"stable@dpdk.org" <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
Akhil Goyal <akhil.goyal@nxp.com>,
"benjamin.walker@intel.com" <benjamin.walker@intel.com>,
David Christensen <drc@linux.vnet.ibm.com>,
"hariprasad.govindharajan@intel.com"
<hariprasad.govindharajan@intel.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>,
"pingx.yu@intel.com" <pingx.yu@intel.com>,
"qian.q.xu@intel.com" <qian.q.xu@intel.com>,
"Raslan Darawsheh" <rasland@oss.nvidia.com>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
"yuan.peng@intel.com" <yuan.peng@intel.com>,
"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>
Subject: Re: [dpdk-stable] 19.11.9 patches review and test
Date: Thu, 1 Jul 2021 15:50:36 +0000 [thread overview]
Message-ID: <DM4PR12MB5167CA40A17F1E0130E12538DA009@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210617063803.3490415-1-christian.ehrhardt@canonical.com>
Hi,
> -----Original Message-----
> From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> Sent: Thursday, June 17, 2021 9:38 AM
> To: stable@dpdk.org
> Cc: dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.com>;
> Akhil Goyal <akhil.goyal@nxp.com>; Ali Alnubani <alialnu@nvidia.com>;
> benjamin.walker@intel.com; David Christensen <drc@linux.vnet.ibm.com>;
> hariprasad.govindharajan@intel.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>; pingx.yu@intel.com; qian.q.xu@intel.com; Raslan
> Darawsheh <rasland@nvidia.com>; NBU-Contact-Thomas Monjalon
> <thomas@monjalon.net>; yuan.peng@intel.com; zhaoyan.chen@intel.com
> Subject: 19.11.9 patches review and test
>
> Hi all,
>
> Here is a list of patches targeted for stable release 19.11.9.
>
> The planned date for the final release is 2nd July.
>
> 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 renewed release candidate tarball can be found at:
>
> https://dpdk.org/browse/dpdk-stable/tag/?id=v19.11.9-rc3
>
> These patches are located at branch 19.11 of dpdk-stable repo:
> https://dpdk.org/browse/dpdk-stable/
>
> Thanks.
>
> Christian Ehrhardt <christian.ehrhardt@canonical.com>
>
The following covers the functional tests that we ran on Mellanox hardware for this release:
- 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:
Items: eth / vlan / ipv4 / ipv6 / tcp / udp / icmp / gre / nvgre / vxlan / ip in ip / mplsoudp / mplsogre
Actions: drop / queue / rss / mark / flag / jump / count / raw_encap / raw_decap / vxlan_encap / vxlan_decap / NAT / dec_ttl
- 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.
Functional tests ran on:
- NIC: ConnectX-4 Lx / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.3-1.0.0.1 / Firmware: 14.30.1004
- NIC: ConnectX-5 / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.3-1.0.0.1 / Firmware: 16.30.1004
We discovered 2 new issues due to environment changes:
- can't create some rules with count action, fixed by https://inbox.dpdk.org/stable/20210621145105.963179-1-lmargalit@nvidia.com/T/#u.
- rte_flow hit counter doesn't increment, still discussing this internally.
Compilation tests with multiple configurations in the following OS/driver combinations are also passing:
- Ubuntu 20.04.2 with MLNX_OFED_LINUX-5.3-1.0.0.1.
- Ubuntu 20.04.2 with rdma-core master (a66e2a5).
- Ubuntu 20.04.2 with rdma-core v28.0.
- Ubuntu 18.04.5 with rdma-core v17.1.
- Ubuntu 18.04.5 with rdma-core master (a66e2a5) (i386).
- Ubuntu 16.04.7 with rdma-core v22.7.
- Fedora 34 with rdma-core v35.0 (only with gcc).
- Fedora 35 (Rawhide) with rdma-core v35.0 (only with gcc).
- CentOS 7 7.9.2009 with rdma-core master (a66e2a5).
- CentOS 7 7.9.2009 with MLNX_OFED_LINUX-5.3-1.0.0.1.
- CentOS 8 8.3.2011 with rdma-core master (7f2d460).
- OpenSUSE Leap 15.3 with rdma-core v31.0.
Note that clang builds are failing in Fedora 34 and 35 due to the following issues:
- https://bugs.dpdk.org/show_bug.cgi?id=745
- https://bugs.dpdk.org/show_bug.cgi?id=733
We don't see any other critical issues blocking this release.
Thanks,
Ali
next prev parent reply other threads:[~2021-07-01 15:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 6:38 Christian Ehrhardt
2021-06-17 17:46 ` Stokes, Ian
2021-06-24 11:05 ` Yu, PingX
2021-07-01 15:50 ` Ali Alnubani [this message]
2021-07-02 6:19 ` Christian Ehrhardt
2021-07-02 7:42 ` Christian Ehrhardt
2021-07-05 6:35 ` Ali Alnubani
2021-07-05 10:44 ` Ali Alnubani
2021-07-05 11:18 ` Christian Ehrhardt
2021-07-05 4:14 ` Pei Zhang
2021-07-05 5:24 ` Christian Ehrhardt
-- strict thread matches above, loose matches on Subject: below --
2021-07-05 13:23 Christian Ehrhardt
2021-07-06 2:45 ` Yu, PingX
2021-07-15 9:13 ` Ali Alnubani
2021-06-02 15:00 Christian Ehrhardt
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=DM4PR12MB5167CA40A17F1E0130E12538DA009@DM4PR12MB5167.namprd12.prod.outlook.com \
--to=alialnu@oss.nvidia.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=akhil.goyal@nxp.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=hariprasad.govindharajan@intel.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=pingx.yu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@oss.nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--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;
as well as URLs for NNTP newsgroup(s).