> -----Original Message----- > From: luca.bocca...@gmail.com <luca.bocca...@gmail.com> > Sent: Saturday, July 29, 2023 2:08 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>; > 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: 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
