From: "Xu, HailinX" <hailinx.xu@intel.com>
To: "Xueming(Steven) Li" <xuemingl@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>
Cc: "xuemingl@nvdia.com" <xuemingl@nvdia.com>,
"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>,
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>,
Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
Raslan Darawsheh <rasland@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Yanghang Liu <yanghliu@redhat.com>,
"Peng, Yuan" <yuan.peng@intel.com>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: RE: 22.11.3 patches review and test
Date: Thu, 31 Aug 2023 01:50:15 +0000 [thread overview]
Message-ID: <MW4PR11MB59121CA8C58163E6DABDCE599FE5A@MW4PR11MB5912.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM4PR12MB53739C288E1BED7A38F4FA9FA1E7A@DM4PR12MB5373.namprd12.prod.outlook.com>
> -----Original Message-----
> From: Xueming(Steven) Li <xuemingl@nvidia.com>
> Sent: Tuesday, August 29, 2023 4:56 PM
> To: Xu, HailinX <hailinx.xu@intel.com>; stable@dpdk.org; Kevin Traynor
> <ktraynor@redhat.com>
> Cc: xuemingl@nvdia.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>; 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>; Luca Boccassi <bluca@debian.org>; Pei Zhang
> <pezhang@redhat.com>; Xu, Qian Q <qian.q.xu@intel.com>; Raslan Darawsheh
> <rasland@nvidia.com>; NBU-Contact-Thomas Monjalon (EXTERNAL)
> <thomas@monjalon.net>; Yanghang Liu <yanghliu@redhat.com>; Peng, Yuan
> <yuan.peng@intel.com>; Chen, Zhaoyan <zhaoyan.chen@intel.com>
> Subject: RE: 22.11.3 patches review and test
>
>
>
> > -----Original Message-----
> > From: Xu, HailinX <hailinx.xu@intel.com>
> > Sent: 8/29/2023 16:22
> > To: Xueming(Steven) Li <xuemingl@nvidia.com>; stable@dpdk.org
> > Cc: xuemingl@nvdia.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>; 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>; NBU-
> > Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>; Yanghang Liu
> > <yanghliu@redhat.com>; Peng, Yuan <yuan.peng@intel.com>; Chen, Zhaoyan
> > <zhaoyan.chen@intel.com>
> > Subject: RE: 22.11.3 patches review and test
> >
> > > -----Original Message-----
> > > From: Xueming Li <xuemingl@nvidia.com>
> > > Sent: Thursday, August 17, 2023 2:14 PM
> > > To: stable@dpdk.org
> > > Cc: xuemingl@nvdia.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>; 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: 22.11.3 patches review and test
> > >
> > > Hi all,
> > >
> > > Here is a list of patches targeted for stable release 22.11.3.
> > >
> > > The planned date for the final release is 31th August.
> > >
> > > 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=v22.11.3-rc1
> > >
> > > These patches are located at branch 22.11 of dpdk-stable repo:
> > > https://dpdk.org/browse/dpdk-stable/
> > >
> > > Thanks.
> >
> > We are conducting DPDK testing and have found two issues.
> >
> > 1. The startup speed of testpmd is significantly slower in the os of SUSE
> > This issue fix patch has been merged into main, But it has not
> > backported to 22.11.3.
> > Fix patch commit id on DPDK main:
> > 7e7b6762eac292e78c77ad37ec0973c0c944b845
>
> Hailin, thanks for the verification and feedback!
> From original patch discussion, the origin decision is no backport, that's why
> "cc:stable@dpdk.org" get removed.
>
> >
> > 2. The SCTP tunnel packet of iavf cannot be forwarded in avx512 mode
> > commit 9b7215f150d0bfc5cb00fce68ff08e5217c7f2b3 on v22.11.3-rc1.
> > This commit is for the new feature (avx512 checksum offload) in DPDK
> > 23.03, which should not be backported to the LTS version since avx512
> > checksum offload is not supported in v22.11.3 LTS.
>
> Okay, I'll revert this patch. Please note the patch has been backported to 21.11,
> Do we want to fix it? @Kevin Traynor
>
> >
> > Regards,
> > Xu, Hailin
Update the test status for Intel part. dpdk22.11.3-rc1 all validation tests done. Found 1 crypto bug.
# Basic Intel(R) NIC testing
* Build & CFLAG compile: cover the build test combination with latest GCC/Clang version and the popular OS revision such as
Ubuntu20.04, Ubuntu22.04, Fedora38, RHEL8.7, RHEL9.2, FreeBSD13.1, SUSE15, CentOS7.9, openEuler22.03-SP1,OpenAnolis8.8 etc.
- All test done. No new dpdk issue is found.
* PF(i40e, ixgbe): test scenarios including RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
- All test done. No new dpdk issue is found.
* VF(i40e, ixgbe): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
- All test done. No new dpdk 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. Here have an issue. Need revert this patch.
The SCTP tunnel packet of iavf cannot be forwarded in avx512 mode.
commit 9b7215f150d0bfc5cb00fce68ff08e5217c7f2b3 on v22.11.3-rc1.
This commit is for the new feature (avx512 checksum offload) in DPDK 23.03, which should not be backported to the LTS version since avx512 checksum offload is not supported in v22.11.3 LTS.
* Intel NIC single core/NIC performance: test scenarios including PF/VF single core performance test, etc.
- All test done. No new dpdk issue is found.
* IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test - QAT&SW/FIB library, etc.
- All test done. No new dpdk issue is found.
# 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 8.0, etc.
- All test done. No new dpdk issue is found.
* Cryptodev:
*Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
- All test done. No new dpdk issue is found.
*Performance test: test scenarios including Thoughput Performance/Cryptodev Latency, etc.
- All test done. Found new bug.
crypto: Performance drop for 1c1t scenario -> Intel dev is under investigating.
Regards,
Xu, Hailin
next prev parent reply other threads:[~2023-08-31 1:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 6:13 Xueming Li
2023-08-24 16:02 ` Ali Alnubani
2023-08-25 6:41 ` Xueming(Steven) Li
2023-08-29 8:22 ` Xu, HailinX
2023-08-29 8:56 ` Xueming(Steven) Li
2023-08-31 1:50 ` Xu, HailinX [this message]
2023-08-31 6:36 ` Xueming(Steven) Li
2023-08-30 16:25 ` Kevin Traynor
2023-08-31 12:17 ` Kevin Traynor
2023-09-01 3:23 ` Zeng, ZhichaoX
2023-09-04 9:32 ` Kevin Traynor
2023-09-04 14:15 ` Kevin Traynor
2023-09-05 1:51 ` Zeng, ZhichaoX
2023-09-05 8:49 ` Kevin Traynor
2023-09-05 9:18 ` Xueming(Steven) Li
2023-09-05 5:37 ` Zeng, ZhichaoX
2023-08-29 16:03 ` YangHang Liu
2023-08-30 5:52 ` 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=MW4PR11MB59121CA8C58163E6DABDCE599FE5A@MW4PR11MB5912.namprd11.prod.outlook.com \
--to=hailinx.xu@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=hemant.agrawal@nxp.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=juhlee@microsoft.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@nvdia.com \
--cc=xuemingl@nvidia.com \
--cc=yanghliu@redhat.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).