From: "Jiang, YuX" <yux.jiang@intel.com>
To: "Xueming(Steven) Li" <xuemingl@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>
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>,
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: 20.11.6 patches review and test
Date: Thu, 25 Aug 2022 02:45:52 +0000 [thread overview]
Message-ID: <BYAPR11MB271127BB0D55A56533C54A97FE729@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM4PR12MB53739E5832632267EFC01940A1709@DM4PR12MB5373.namprd12.prod.outlook.com>
> -----Original Message-----
> From: Xueming(Steven) Li <xuemingl@nvidia.com>
> Sent: Tuesday, August 23, 2022 7:51 PM
> To: Jiang, YuX <yux.jiang@intel.com>; 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>; 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: 20.11.6 patches review and test
>
>
>
> > -----Original Message-----
> > From: Jiang, YuX <yux.jiang@intel.com>
> > Sent: Tuesday, August 23, 2022 5:39 PM
> > To: Xueming(Steven) Li <xuemingl@nvidia.com>; 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>;
> > 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: 20.11.6 patches review and test
> >
> > > -----Original Message-----
> > > From: Xueming(Steven) Li <xuemingl@nvidia.com>
> > > Sent: Wednesday, August 17, 2022 2:10 PM
> > > To: Jiang, YuX <yux.jiang@intel.com>; 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>; 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: 20.11.6 patches review and test
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Jiang, YuX <yux.jiang@intel.com>
> > > > Sent: Wednesday, August 17, 2022 11:23 AM
> > > > To: Xueming(Steven) Li <xuemingl@nvidia.com>; 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>; 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: 20.11.6 patches review and test
> > > >
> > > > > -----Original Message-----
> > > > > From: Xueming Li <xuemingl@nvidia.com>
> > > > > Sent: Monday, August 15, 2022 5:17 PM
> > > > > 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>; 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: 20.11.6 patches review and test
> > > > >
> > > > > Hi all,
> > > > >
> > > > > Here is a list of patches targeted for stable release 20.11.6.
> > > > >
> > > > > 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=v20.11.6-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>
> > > > >
> > > > > ---
> > > > Hi Xueming,
> > > >
> > > > We found one kni build bug
> > > > https://bugs.dpdk.org/show_bug.cgi?id=1066,
> > > which will block build when kmods=True.
> > > > And this is a fix https://git.dpdk.org/dpdk/commit/?id=327ef506599
> > > > can be
> > > applied on LTS20.11 and verified passed.
> > > > So could you pls merge it into LTS20.11? Thanks~
> > >
> > > Patch merged and pushed. Thanks for identifying the problem!
> > >
> > Thanks Xueming,
> > One unit test issue for link_bonding_rssconf
> https://bugs.dpdk.org/show_bug.cgi?id=1070, we verify below patch passed
> on LTS20.11.
> > please merge it into 20.11:
> > https://git.dpdk.org/dpdk-stable/commit/?h=v19.11.13-
> rc3&id=f0bda10005
> > d89d18f69055cb9e7780c7702a8292
> > ethdev: fix RSS update when RSS is disabled Thanks.
> >
>
> Thanks for reminding.
> The patch scanning scripts excluded this patch because it "fixes" patch of the
> year 2021. Merged.
>
> Also merged a vhost async patch from Jiayu, let me know if any concerns:
> https://mails.dpdk.org/archives/stable/2022-August/039949.html
>
Update the test status for Intel part. Till now dpdk20.11.6-rc1 validation test is almost finished. No critical issue is found.
And also verify below bugs' patch passed for latest LTS20.11(https://git.dpdk.org/dpdk-stable/commit/?h=20.11&id=28596f9ebca8e04f6711458839629960afcc6091).
Bug 1066 - [dpdk20.11.6-rc1] dpdk20.11.6-rc1 compiled failed with kmods enable
Bug 1070 - [dpdk-20.11.6-rc1] unit_tests_eal/link_bonding_rssconf: link_bonding_rssconf_autotest test failed
# 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, Fedora36, RHEL8.4, etc.
- All test done. One known bug: https://bugs.dpdk.org/show_bug.cgi?id=991 [19.11] net/ena build failure with gcc 12, still no fix.
* 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. No new dpdk issue is found.
* Intel NIC single core/NIC performance: test scenarios including PF/VF single core 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 test 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 passed.
*Performance test: test scenarios including Thoughput Performance /Cryptodev Latency, etc.
- All test done.
Best regards,
Yu Jiang
next prev parent reply other threads:[~2022-08-25 2:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 9:16 Xueming Li
2022-08-17 3:22 ` Jiang, YuX
2022-08-17 6:09 ` Xueming(Steven) Li
2022-08-23 9:38 ` Jiang, YuX
2022-08-23 11:51 ` Xueming(Steven) Li
2022-08-25 2:45 ` Jiang, YuX [this message]
2022-08-25 5:44 ` Xueming(Steven) Li
2022-08-23 14:54 ` Ali Alnubani
2022-08-25 5:45 ` Xueming(Steven) Li
2022-08-24 14:44 ` YangHang Liu
2022-08-25 5:45 ` Xueming(Steven) Li
2022-08-29 13:02 ` Stokes, Ian
2022-08-29 13:04 ` 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=BYAPR11MB271127BB0D55A56533C54A97FE729@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=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=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).