From: Ali Alnubani <alialnu@nvidia.com>
To: "christian.ehrhardt@canonical.com"
<christian.ehrhardt@canonical.com>,
"stable@dpdk.org" <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Abhishek Marathe <Abhishek.Marathe@microsoft.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>,
"qian.q.xu@intel.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" <yuan.peng@intel.com>,
"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>
Subject: RE: 19.11.13 patches review and test
Date: Thu, 18 Aug 2022 16:11:20 +0000 [thread overview]
Message-ID: <DM4PR12MB51672ADEC9F17658604A5B73DA6D9@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220804082154.1954244-1-christian.ehrhardt@canonical.com>
> -----Original Message-----
> From: christian.ehrhardt@canonical.com
> <christian.ehrhardt@canonical.com>
> Sent: Thursday, August 4, 2022 11:22 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>; Luca Boccassi <bluca@debian.org>; 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: 19.11.13 patches review and test
>
> Hi all,
>
> This is -rc3 just after -rc2 as a build issue was hiding in the former.
> Sorry for the extra noise, but other than that it all stays the same.
>
> there were three patches close to the deadline that I missed and I
> considered postponing them to 19.11.14 at first. But in the meantime
> there arrived 11 more and I think that justfies a new tag for 19.11.13.
>
> We still have almost 4 weeks left - I hope that is ok.
>
> Here is the combined list of patches (the same as before plus the new 14)
> targeted for stable release 19.11.13.
>
> The planned date for the final release is August 29th.
>
> 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=v19.11.13-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>
>
Hello,
We ran the following functional tests with Nvidia hardware on 19.11.13-rc3:
- 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 / ipv4 / ipv6 / tcp / udp / icmp / gre / nvgre / geneve / vxlan / 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.5-1.0.3.2 / Firmware: 14.32.1010
- NIC: ConnectX-5 / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.5-1.0.3.2 / Firmware: 16.32.1010
Additionally, we ran compilation tests with multiple configurations in the following OS/driver combinations:
- Ubuntu 20.04.4 with MLNX_OFED_LINUX-5.7-1.0.2.0.
- Ubuntu 20.04.4 with rdma-core master (23a0021).
- Ubuntu 20.04.4 with rdma-core v28.0.
- Ubuntu 18.04.6 with rdma-core v17.1.
- Ubuntu 18.04.6 with rdma-core master (23a0021) (i386).
- Ubuntu 16.04.7 with rdma-core v22.7.
- Fedora 35 with rdma-core v39.0 (with gcc only).
- Fedora 37 (Rawhide) with rdma-core v39.0 (with clang only).
- CentOS 7 7.9.2009 with rdma-core master (23a0021).
- CentOS 7 7.9.2009 with MLNX_OFED_LINUX-5.7-1.0.2.0.
- CentOS 8 8.4.2105 with rdma-core master (23a0021).
- OpenSUSE Leap 15.4 with rdma-core v38.1.
We don't see any issues introduced by changes in this rc.
Thanks,
Ali
next prev parent reply other threads:[~2022-08-18 16:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 8:21 christian.ehrhardt
2022-08-11 7:37 ` Jiang, YuX
2022-08-11 7:50 ` Christian Ehrhardt
2022-08-18 16:11 ` Ali Alnubani [this message]
2022-08-19 5:32 ` YangHang Liu
-- strict thread matches above, loose matches on Subject: below --
2022-08-03 10:29 christian.ehrhardt
2022-07-18 10:17 christian.ehrhardt
2022-07-19 2:43 ` Pei Zhang
2022-07-19 5:27 ` Christian Ehrhardt
2022-08-03 4:39 ` YangHang Liu
2022-08-03 10:19 ` Christian Ehrhardt
2022-07-29 12:08 ` Jiang, YuX
2022-08-03 10:19 ` 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=DM4PR12MB51672ADEC9F17658604A5B73DA6D9@DM4PR12MB5167.namprd12.prod.outlook.com \
--to=alialnu@nvidia.com \
--cc=Abhishek.Marathe@microsoft.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=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=qian.q.xu@intel.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yanghliu@redhat.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).