RE: 19.11.13 patches review and test

["Jiang, YuX" <yux.jiang@intel.com>]

> -----Original Message-----
> From: christian.ehrhardt@canonical.com <christian.ehrhardt@canonical.com>
> Sent: Thursday, August 4, 2022 4:22 PM
> To: stable@dpdk.org
> Cc: dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.com>;
> Ali Alnubani <alialnu@nvidia.com>; Walker, Benjamin
> <benjamin.walker@intel.com>; David Christensen
> <drc@linux.vnet.ibm.com>; Hemant Agrawal <hemant.agrawal@nxp.com>;
> Stokes, Ian <ian.stokes@intel.com>; Jerin Jacob <jerinj@marvell.com>;
> Mcnamara, John <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>; Xu, Qian
> Q <qian.q.xu@intel.com>; Raslan Darawsheh <rasland@nvidia.com>;
> Thomas Monjalon <thomas@monjalon.net>; Yanghang Liu
> <yanghliu@redhat.com>; Peng, Yuan <yuan.peng@intel.com>; Chen,
> Zhaoyan <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>
> 
> ---
Update the test status for Intel part. DPDK19.11.13-rc3 almost test finished, no critical issue is found, but also find some new bugs on FreeBSD13.0.
New report defects for build:
  1, https://bugs.dpdk.org/show_bug.cgi?id=1064 [19.11.13-rc3] lib/eal make build failed with gcc10.3.0 and clang11.0.1 on FreeBSD13.0/64
	> Not found such issue on FreeBSD13.1
  2, https://bugs.dpdk.org/show_bug.cgi?id=1063 [19.11.13-rc3] drivers/net/i40e on meson build failure with clang13.0 on FreeBSD13.1/64
	> Not found such issue on FreeBSD13.0, Intel Dev is investigating.
Known defects for build:
  1, [dpdk 19.11.13-rc1] lib/librte_eal meson build error with gcc12.1 on fedora36, similar as https://bugs.dpdk.org/show_bug.cgi?id=985
	> Not found such issue on Fedora35. Dev said that looks like a GCC13 BUG
  2, [dpdk 19.11.13-rc1] drivers/net/ena make build error with gcc12.1 on fedora36, similar as https://bugs.dpdk.org/show_bug.cgi?id=991
	> No update in bugzilla, no fix yet.
  3, https://bugs.dpdk.org/show_bug.cgi?id=912 [dpdk 19.11.13-rc1] drivers/net/qede make build error with clang14 on fedora36/redhat8.6/UB22.04
	> Known issue, no update in bugzilla, no fix yet.

# Basic Intel(R) NIC testing
* Build: cover the build test combination with latest GCC/Clang version and the popular OS revision such as Ubuntu20.04&22.04, Fedora36, RHEL8.4, etc.
	- All test done. 
* PF&VF(i40e, ixgbe): test scenarios including RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc. 
	- All test done. No new bug is found.
* PF/VF(ice): test scenarios including Switch features/Package Management/Flow Director/Advanced Tx, etc.
	- All test done. No new issue is found. 
	- Known bug about [dpdk-19.11.12] metering_and_policing/ipv4_HASH_table_RFC2698: unable to forward packets normally. Intel Dev is still investigating.
* Intel NIC single core/NIC performance: test scenarios including PF/VF single core performance test etc.
	- All test done. No big performance drop.
		
# Basic cryptodev and virtio testing
* Virtio: both function and performance test are covered. Such as PVP/Virtio_loopback/virtio-user loopback/virtio-net VM2VM perf testing, etc.
	- All test done. No new issue is found.
* Cryptodev: 
* Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/ etc.
	- All test done. No new issue is found.
* Performance test: test scenarios including Thoughput Performance /Cryptodev Latency, etc.
	- All test done. No performance drop.

Best regards,
Yu Jiang