DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Jiang, YuX" <yux.jiang@intel.com>
To: "luca.boccassi@gmail.com" <luca.boccassi@gmail.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>,
	Thomas Monjalon <thomas@monjalon.net>,
	"Peng, Yuan" <yuan.peng@intel.com>,
	"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: RE: 20.11.5 patches review and test
Date: Wed, 30 Mar 2022 10:01:28 +0000	[thread overview]
Message-ID: <BYAPR11MB2711B1FFA172AFDFAA3E133CFE1F9@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BYAPR11MB271135C5D6C8A7B4C66548E7FE1E9@BYAPR11MB2711.namprd11.prod.outlook.com>

> -----Original Message-----
> From: Jiang, YuX
> Sent: Tuesday, March 29, 2022 7:48 PM
> To: luca.boccassi@gmail.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>;
> Thomas Monjalon <thomas@monjalon.net>; Peng, Yuan
> <yuan.peng@intel.com>; Chen, Zhaoyan <zhaoyan.chen@intel.com>
> Subject: RE: 20.11.5 patches review and test
> 
> > -----Original Message-----
> > From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> > Sent: Friday, March 18, 2022 11:21 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>; 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.5 patches review and test
> >
> > Hi all,
> >
> > Here is a list of patches targeted for stable release 20.11.5.
> >
> > The planned date for the final release is the 4th of April.
> >
> > 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.5-rc1
> >
> > These patches are located at branch 20.11 of dpdk-stable repo:
> >     https://dpdk.org/browse/dpdk-stable/
> >
> > Thanks.
> >
> > Luca Boccassi
> >
> > ---
> Hi Luca,
> 
> Update the test status for Intel part. Till now dpdk20.11.5-rc1 test rate is 90%.
> Till now, no critical issue is found.
> # Basic Intel(R) NIC testing
> * Build&CFLAG compile: cover the build test combination with latest
> GCC/Clang/ICC version and the popular OS revision such as Ubuntu20.04,
> Fedora35, RHEL8.4, etc.
> - All test done. One bug https://bugs.dpdk.org/show_bug.cgi?id=982, no fix
> yet.
> * PF(i40e, ixgbe): test scenarios including
> RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
> - Execution rate is 90%. No new issue is found.
> * VF(i40e, ixgbe): test scenarios including VF-
> RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
> 
> - Execution rate is 90%. 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.
> - Execution rate is 90%. 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 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. Find 5 cbdma related defects, Intel dev is investigating them.
> * 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

Update the test status for Intel part. Till now dpdk20.11.5-rc1 is almost finished, no critical issue is found.
# Basic Intel(R) NIC testing
* Build&CFLAG compile: cover the build test combination with latest GCC/Clang/ICC version and the popular OS revision such as Ubuntu20.04, Fedora35, RHEL8.4, etc.
- All test done. One bug https://bugs.dpdk.org/show_bug.cgi?id=982, no fix yet.
* 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, 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 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

  parent reply	other threads:[~2022-03-30 10:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 15:20 luca.boccassi
2022-03-23 13:33 ` Pei Zhang
2022-03-23 15:36   ` Luca Boccassi
2022-03-28  7:40 ` Christian Ehrhardt
2022-03-28 11:50   ` Luca Boccassi
2022-03-28 12:55     ` Christian Ehrhardt
2022-03-28 15:29       ` Luca Boccassi
2022-03-31 10:50         ` Christian Ehrhardt
2022-03-31 12:55           ` Luca Boccassi
2022-03-29 11:48 ` Jiang, YuX
2022-03-29 12:12   ` Luca Boccassi
2022-03-30 10:01   ` Jiang, YuX [this message]
2022-03-30  8:22 ` Ali Alnubani

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=BYAPR11MB2711B1FFA172AFDFAA3E133CFE1F9@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=luca.boccassi@gmail.com \
    --cc=pezhang@redhat.com \
    --cc=qian.q.xu@intel.com \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --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).