> -----Original Message----- > From: christian.ehrha...@canonical.com > <christian.ehrha...@canonical.com> > Sent: Thursday, August 4, 2022 11:22 AM > To: sta...@dpdk.org > Cc: dev@dpdk.org; Abhishek Marathe <abhishek.mara...@microsoft.com>; > Ali Alnubani <alia...@nvidia.com>; benjamin.wal...@intel.com; David > Christensen <d...@linux.vnet.ibm.com>; Hemant Agrawal > <hemant.agra...@nxp.com>; Ian Stokes <ian.sto...@intel.com>; Jerin > Jacob <jer...@marvell.com>; John McNamara <john.mcnam...@intel.com>; > Ju-Hyoung Lee <juh...@microsoft.com>; Kevin Traynor > <ktray...@redhat.com>; Luca Boccassi <bl...@debian.org>; Pei Zhang > <pezh...@redhat.com>; qian.q...@intel.com; Raslan Darawsheh > <rasl...@nvidia.com>; NBU-Contact-Thomas Monjalon (EXTERNAL) > <tho...@monjalon.net>; Yanghang Liu <yangh...@redhat.com>; > yuan.p...@intel.com; zhaoyan.c...@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.ehrha...@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
