From: Ali Alnubani <alialnu@nvidia.com>
To: "luca.boccassi@gmail.com" <luca.boccassi@gmail.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>,
"Ali Alnubani" <alialnu@mellanox.com>,
"benjamin.walker@intel.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>,
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@mellanox.com>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
"yuan.peng@intel.com" <yuan.peng@intel.com>,
"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [dpdk-dev] 19.11.6 patches review and test
Date: Wed, 16 Dec 2020 20:34:12 +0000 [thread overview]
Message-ID: <DM6PR12MB4910B33001F57B7BCFEFEB07DAC50@DM6PR12MB4910.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20201203093856.299103-1-luca.boccassi@gmail.com>
Hi,
> -----Original Message-----
> From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> Sent: Thursday, December 3, 2020 11:39 AM
> To: stable@dpdk.org
> Cc: dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.com>;
> Akhil Goyal <akhil.goyal@nxp.com>; Ali Alnubani <alialnu@mellanox.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>; Luca Boccassi <bluca@debian.org>;
> Pei Zhang <pezhang@redhat.com>; pingx.yu@intel.com;
> qian.q.xu@intel.com; Raslan Darawsheh <rasland@mellanox.com>; NBU-
> Contact-Thomas Monjalon <thomas@monjalon.net>; yuan.peng@intel.com;
> zhaoyan.chen@intel.com
> Subject: 19.11.6 patches review and test
>
> Hi all,
>
> Here is a list of patches targeted for stable release 19.11.6.
>
> The planned date for the final release is December 17.
>
> 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.
>
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.
- Some RSS tests.
- VLAN stripping and insertion tests.
- Checksum and TSO tests.
- ptype tests.
- l3fwd-power example application tests.
- Multi-process example applications tests.
The tests ran on:
- NIC: ConnectX-4 Lx / OS: RHEL7.4 / Driver: MLNX_OFED_LINUX-5.1-2.5.8.0 / Firmware: 14.28.2006
- NIC: ConnectX-5 / OS: RHEL7.4 / Driver: MLNX_OFED_LINUX-5.1-2.5.8.0 / Firmware: 16.28.2006
Compilation tests in the following OS/driver combinations are also passing:
- Ubuntu 20.04 with MLNX_OFED_LINUX-5.1-2.5.8.0.
- Ubuntu 20.04 with rdma-core master (6a5c1b7).
- Ubuntu 20.04 with rdma-core v28.0.
- Ubuntu 18.04 with rdma-core v17.1.
- Ubuntu 18.04 with rdma-core master (6a5c1b7) (i386).
- Ubuntu 16.04 with rdma-core v22.7.
- Fedora 32 with rdma-core v32.0.
- CentOS 7 7.9.2009 with rdma-core master (6a5c1b7).
- CentOS 7 7.9.2009 with MLNX_OFED_LINUX-5.1-2.5.8.0.
- CentOS 8 8.3.2011 with rdma-core master (6a5c1b7).
- openSUSE Leap 15.2 with rdma-core v27.1.
The testing was done on v19.11.6-rc1 with the following patch applied:
http://inbox.dpdk.org/stable/1608132648-15469-1-git-send-email-viacheslavo@nvidia.com/T/#u
We don't see any critical issues blocking the release other than the debug build failure Viacheslav fixed.
Regards,
Ali
next prev parent reply other threads:[~2020-12-16 20:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 9:38 luca.boccassi
2020-12-10 10:07 ` Chen, BoX C
2020-12-10 10:15 ` Luca Boccassi
2020-12-16 10:08 ` Luca Boccassi
2020-12-17 9:50 ` Yu, PingX
2020-12-17 10:40 ` Yu, DapengX
2020-12-17 10:59 ` Luca Boccassi
2020-12-18 2:45 ` Yu, DapengX
2020-12-18 10:09 ` Luca Boccassi
2020-12-10 16:58 ` [dpdk-dev] [EXTERNAL] " Abhishek Marathe
2020-12-10 18:25 ` Luca Boccassi
2020-12-16 8:47 ` [dpdk-dev] " Pei Zhang
2020-12-16 10:10 ` Luca Boccassi
2020-12-16 12:11 ` Govindharajan, Hariprasad
2020-12-16 13:16 ` Luca Boccassi
2020-12-16 20:34 ` Ali Alnubani [this message]
2020-12-17 9:39 ` 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=DM6PR12MB4910B33001F57B7BCFEFEB07DAC50@DM6PR12MB4910.namprd12.prod.outlook.com \
--to=alialnu@nvidia.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=akhil.goyal@nxp.com \
--cc=alialnu@mellanox.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.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=luca.boccassi@gmail.com \
--cc=pezhang@redhat.com \
--cc=pingx.yu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@mellanox.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.com \
--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).