> -----Original Message----- > From: Jiang, YuX <yux.ji...@intel.com> > Sent: Thursday, December 9, 2021 6:01 PM > To: Xueming Li <xuemi...@nvidia.com>; sta...@dpdk.org; Lin, Xueqin > <xueqin....@intel.com> > Cc: dev@dpdk.org; Abhishek Marathe <abhishek.mara...@microsoft.com>; > Ali Alnubani <alia...@nvidia.com>; Walker, Benjamin > <benjamin.wal...@intel.com>; David Christensen > <d...@linux.vnet.ibm.com>; Govindharajan, Hariprasad > <hariprasad.govindhara...@intel.com>; Hemant Agrawal > <hemant.agra...@nxp.com>; Stokes, Ian <ian.sto...@intel.com>; Jerin > Jacob <jer...@marvell.com>; Mcnamara, John <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>; Xu, Qian Q <qian.q...@intel.com>; Raslan > Darawsheh <rasl...@nvidia.com>; Thomas Monjalon > <tho...@monjalon.net>; Peng, Yuan <yuan.p...@intel.com>; Chen, > Zhaoyan <zhaoyan.c...@intel.com> > Subject: RE: 20.11.4 patches review and test > > > -----Original Message----- > > From: Xueming Li <xuemi...@nvidia.com> > > Sent: Tuesday, December 7, 2021 12:15 AM > > To: sta...@dpdk.org > > Cc: xuemi...@nvidia.com; dev@dpdk.org; Abhishek Marathe > > <abhishek.mara...@microsoft.com>; Ali Alnubani <alia...@nvidia.com>; > > Walker, Benjamin <benjamin.wal...@intel.com>; David Christensen > > <d...@linux.vnet.ibm.com>; Govindharajan, Hariprasad > > <hariprasad.govindhara...@intel.com>; Hemant Agrawal > > <hemant.agra...@nxp.com>; Stokes, Ian <ian.sto...@intel.com>; Jerin > > Jacob <jer...@marvell.com>; Mcnamara, John > <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>; Xu, Qian Q <qian.q...@intel.com>; Raslan > > Darawsheh <rasl...@nvidia.com>; Thomas Monjalon > <tho...@monjalon.net>; > > Peng, Yuan <yuan.p...@intel.com>; Chen, Zhaoyan > > <zhaoyan.c...@intel.com> > > Subject: 20.11.4 patches review and test > > > > Hi all, > > > > Here is a list of patches targeted for stable release 20.11.4. > > > > The planned date for the final release is 31th December. > > > > 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.4-rc1 > > > > These patches are located at branch 20.11 of dpdk-stable repo: > > https://dpdk.org/browse/dpdk-stable/ > > > > Thanks. > > > > Xueming Li <xuemi...@nvidia.com> > > > Update the test status for Intel part. Till now dpdk20.11.4-rc1 test execution > rate is 80%. Currently, find three bugs, two bugs have fix now. > # Basic Intel(R) NIC testing > * Build or compile: > *Build: cover the build test combination with latest GCC/Clang/ICC > version and the popular OS revision such as Ubuntu20.04, Fedora34, RHEL8.4, > etc. > - All test done. > - Two bugs are found in 20.11.4-rc1. > - dpdk-20.11.4]kernel/linux/kni/rte_kni.ko build > failed on OpenSuse15.3 with gcc7.5.0&clang11.0.1 > - fix link: > http://inbox.dpdk.org/stable/20211208103410.835542-1- > ferruh.yi...@intel.com/T/#u , verify passed by Intel > - https://bugs.dpdk.org/show_bug.cgi?id=894 > [dpdk-20.11.4] lib/librte_eal.a.p/librte_eal_common_rte_random.c.obj build > failed on WIN10 with clang8.0.0 > - fix link: > http://inbox.dpdk.org/stable/20211207141644.369624-1- > dmitry.kozl...@gmail.com/T/#u, verify passed by Intel > * PF(i40e, ixgbe): test scenarios including > RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc. > - All test done. No new issue is found. > * VF(i40e, ixgbe): test scenarios including VF- > RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc. > > - All test done. No new issue is found. > * PF/VF(ice): test scenarios including Switch features/Package > Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Share > code update/Flexible Descriptor, etc. > - Execution rate is 80%. No new issue is found. > * Intel NIC single core/NIC performance: test scenarios including > PF/VF single core performance test, RFC2544 Zero packet loss performance > test, etc. > - Execution rate is 50%. No big performance drop. > * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic > test - QAT&SW/FIB library, etc. > - All passed. > # 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/VMAWARE ESXI 7.0u3, etc. > - Execution rate is 80%. No new issue is found. > * Cryptodev: > *Function test: test scenarios including Cryptodev API > testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc. > - All test done. > - One new bug about "[dpdk-LTS-20.11.4-rc1] > cryptodev_qat_asym_autotest is failing" is found, Intel dev is under > investigating. > bad commit id is commit > 2f2c2b5b7e7ae4942b4b3686bce2eb856fee447d > Author: Przemyslaw Zegan > <przemyslawx.ze...@intel.com> > Date: Wed Nov 3 15:08:23 2021 +0000 > common/qat: fix queue pairs number > *Performance test: test scenarios including Thoughput > Performance /Cryptodev Latency, etc. > - All test done.
Update the test status for Intel part. Till now dpdk20.11.4-rc1 test is almost finished. Totally find three bugs, two bugs have fix now. # Basic Intel(R) NIC testing * Build: cover the build test combination with latest GCC/Clang/ICC version and the popular OS revision such as Ubuntu20.04, Fedora34, RHEL8.4, etc. - All test done. - Two bugs are found in 20.11.4-rc1. Bug1, "dpdk-20.11.4]kernel/linux/kni/rte_kni.ko build failed on OpenSuse15.3 with gcc7.5.0&clang11.0.1" Has fix link: http://inbox.dpdk.org/stable/20211208103410.835542-1-ferruh.yi...@intel.com/T/#u Bug2, "https://bugs.dpdk.org/show_bug.cgi?id=894 [dpdk-20.11.4] lib/librte_eal.a.p/librte_eal_common_rte_random.c.obj build failed on WIN10 with clang8.0.0" Has fix link: http://inbox.dpdk.org/stable/20211207141644.369624-1-dmitry.kozl...@gmail.com/T/#u * PF(i40e, ixgbe): test scenarios including RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc. - All test done. No new issue is found. * VF(i40e, ixgbe): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc. - All test done. No new issue is found. * PF/VF(ice): test scenarios including Switch features/Package Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Flexible Descriptor, etc. - All test done. No new issue is found. * Intel NIC single core/NIC performance: test scenarios including PF/VF single core performance test, RFC2544 Zero packet loss performance test, etc. - All test done. No big performance drop. * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test - QAT&SW/FIB library, etc. - All passed. # 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/VMAWARE ESXI 7.0u3, 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/FIPS, etc. - All test done. Find one bug , Intel dev is under investigating. - Bug3 "[dpdk-LTS-20.11.4-rc1] cryptodev_qat_asym_autotest is failing" bad commit id is commit 2f2c2b5b7e7ae4942b4b3686bce2eb856fee447d Author: Przemyslaw Zegan <przemyslawx.ze...@intel.com> Date: Wed Nov 3 15:08:23 2021 +0000 common/qat: fix queue pairs number *Performance test: test scenarios including Thoughput Performance /Cryptodev Latency, etc. - All test done.
