DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Jiang, YuX" <yux.jiang@intel.com>
To: "Jiang, YuX" <yux.jiang@intel.com>,
	Xueming Li <xuemingl@nvidia.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"Lin, Xueqin" <xueqin.lin@intel.com>
Cc: "dev@dpdk.org" <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>,
	"Govindharajan, Hariprasad" <hariprasad.govindharajan@intel.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>,
	"Peng, Yuan" <yuan.peng@intel.com>,
	"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: RE: 20.11.4 patches review and test
Date: Fri, 10 Dec 2021 11:35:51 +0000	[thread overview]
Message-ID: <BYAPR11MB2711F0B9DEF1A0351F882778FE719@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BYAPR11MB271117E9B20296F9CF3BF17AFE709@BYAPR11MB2711.namprd11.prod.outlook.com>

> -----Original Message-----
> From: Jiang, YuX <yux.jiang@intel.com>
> Sent: Thursday, December 9, 2021 6:01 PM
> To: Xueming Li <xuemingl@nvidia.com>; stable@dpdk.org; Lin, Xueqin
> <xueqin.lin@intel.com>
> 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>; Govindharajan, Hariprasad
> <hariprasad.govindharajan@intel.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>; Peng, Yuan <yuan.peng@intel.com>; Chen,
> Zhaoyan <zhaoyan.chen@intel.com>
> Subject: RE: 20.11.4 patches review and test
> 
> > -----Original Message-----
> > From: Xueming Li <xuemingl@nvidia.com>
> > Sent: Tuesday, December 7, 2021 12:15 AM
> > To: stable@dpdk.org
> > Cc: xuemingl@nvidia.com; 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>; Govindharajan, Hariprasad
> > <hariprasad.govindharajan@intel.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>;
> > Peng, Yuan <yuan.peng@intel.com>; Chen, Zhaoyan
> > <zhaoyan.chen@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 <xuemingl@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.yigit@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.kozliuk@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.zegan@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.yigit@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.kozliuk@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.zegan@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.

  reply	other threads:[~2021-12-10 11:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06 16:15 Xueming Li
2021-12-09 10:01 ` Jiang, YuX
2021-12-10 11:35   ` Jiang, YuX [this message]
2021-12-15 14:44     ` Xueming(Steven) Li
2021-12-16  6:40       ` Jiang, YuX
2021-12-23 15:07         ` Xueming(Steven) Li
2022-01-12  9:53           ` Zhang, Roy Fan
2022-01-12 11:01             ` Xueming(Steven) Li
2022-01-12 11:29               ` Jiang, YuX
2022-01-12 12:53                 ` Xueming(Steven) Li
2021-12-13 14:27 ` Pei Zhang
2021-12-15 14:46   ` Xueming(Steven) Li
2021-12-23 14:52 ` Ali Alnubani
2021-12-23 15:08   ` Xueming(Steven) Li

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BYAPR11MB2711F0B9DEF1A0351F882778FE719@BYAPR11MB2711.namprd11.prod.outlook.com \
    --to=yux.jiang@intel.com \
    --cc=Abhishek.Marathe@microsoft.com \
    --cc=alialnu@nvidia.com \
    --cc=benjamin.walker@intel.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=hariprasad.govindharajan@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=ian.stokes@intel.com \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=juhlee@microsoft.com \
    --cc=ktraynor@redhat.com \
    --cc=pezhang@redhat.com \
    --cc=qian.q.xu@intel.com \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=xuemingl@nvidia.com \
    --cc=xueqin.lin@intel.com \
    --cc=yuan.peng@intel.com \
    --cc=zhaoyan.chen@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).