RE: 19.11.11 (RC2) patches review and test

-----Original Message-----
From: christian.ehrhardt@canonical.com
[off-list ref]
Sent: Monday, December 20, 2021 10:00 AM
To: stable@dpdk.org
Cc: dev@dpdk.org; Abhishek Marathe <redacted>;
Akhil Goyal [off-list ref]; Ali Alnubani [off-list ref];
benjamin.walker@intel.com; David Christensen [off-list ref];
Hemant Agrawal [off-list ref]; Ian Stokes
[off-list ref]; Jerin Jacob [off-list ref]; John McNamara
[off-list ref]; Ju-Hyoung Lee [off-list ref];
Kevin Traynor [off-list ref]; Luca Boccassi [off-list ref];
Pei Zhang [off-list ref]; pingx.yu@intel.com;
qian.q.xu@intel.com; Raslan Darawsheh [off-list ref]; NBU-
Contact-Thomas Monjalon (EXTERNAL) [off-list ref];
yuan.peng@intel.com; zhaoyan.chen@intel.com
Subject: 19.11.11 (RC2) patches review and test

Hi all,

Here is a list of patches targeted for stable release 19.11.11.

The planned date for the final release is 7th January 2021.

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.

This -rc2 is supposed to be functionally equivalent to the -rc1 version
we had 11 days ago. The only fixes added since v19.11.11-rc1 are for
typos (in comments) and to fix compilation issues on some kernels
and newer toolchains. We still can't build everything with clang13 (19.11
never built there, this is not a regression), but various issues blocking
that are resolved already. The issues with SLES15 kernels are resolved as
well as using LTO with gcc 10 is fixed.

Therefore there is no strict need to rerun all tests on -rc2 - OTOH by all
means if you have the time and capacity I'd absolutely appreciate if
you could do so.
What is important and should be tested are various builds, to ensure that
none of these changes broke a build for those target platforms that worked
before.
And furthermore - if before you had further functional tests blocked by
those build issues - then now you can build and run those further tests
that were formerly blocked.

List of fixed bugs since -rc1:
- https://bugs.dpdk.org/show_bug.cgi?id=745
- https://bugs.dpdk.org/show_bug.cgi?id=900
- https://bugs.dpdk.org/show_bug.cgi?id=901
- https://bugs.dpdk.org/show_bug.cgi?id=902
- https://bugs.dpdk.org/show_bug.cgi?id=903
- https://bugs.dpdk.org/show_bug.cgi?id=907
- https://bugs.dpdk.org/show_bug.cgi?id=908
- Build on FreeBSD 13 (had no bug number)

Known and still remaining are:
- https://bugs.dpdk.org/show_bug.cgi?id=744
- https://bugs.dpdk.org/show_bug.cgi?id=747
- https://bugs.dpdk.org/show_bug.cgi?id=904
- https://bugs.dpdk.org/show_bug.cgi?id=905
- https://bugs.dpdk.org/show_bug.cgi?id=912

For everyone helping to fix so many of them already, thank you a lot!
Maybe not on 19.11.11, if the joint efforts continue maybe 19.11.12
will be able to resolve all these issues that are currently left.
So keep the patches coming. Even after 19.11.11 is released I'll continue
to enqueue your build fixes and since we just extended the lifetime of 19.11
to three years there will be a 19.11.12 coming to pick them up.

Hi,

The following covers the functional tests that we ran on Nvidia 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 / 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-4 Lx / OS: Ubuntu 20.04 LTS / Kernel: 5.16.0-rc7 / Driver: rdma-core v38.0 / 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
- NIC: ConnectX-5 / OS: Ubuntu 20.04 LTS / Kernel: 5.16.0-rc7 / Driver: v38.0 / Firmware: 16.32.1010

Compilation tests with multiple configurations in the following OS/driver combinations are also passing:
- Ubuntu 20.04.3 with MLNX_OFED_LINUX-5.5-1.0.3.2.
- Ubuntu 20.04.3 with rdma-core master (c52b43e).
- Ubuntu 20.04.3 with rdma-core v28.0.
- Ubuntu 18.04.6 with rdma-core v17.1.
- Ubuntu 18.04.6 with rdma-core master (c52b43e) (i386).
- Ubuntu 16.04.7 with rdma-core v22.7.
- Fedora 35 with rdma-core v38.0 (passing except for make builds with clang, see: https://bugs.dpdk.org/show_bug.cgi?id=912).
- Fedora 36 (Rawhide) with rdma-core v38.0
- CentOS 7 7.9.2009 with rdma-core master (940f53f).
- CentOS 7 7.9.2009 with MLNX_OFED_LINUX-5.5-1.0.3.2.
- CentOS 8 8.4.2105 with rdma-core master (940f53f).
- OpenSUSE Leap 15.3 with rdma-core v31.0.

We don't see any other new issues in this release.

Thanks,
Ali