patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Jiang, YuX" <yux.jiang@intel.com>
To: Luca Boccassi <bluca@debian.org>, "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>,
	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>,
	"yanghliu@redhat.com" <yanghliu@redhat.com>
Subject: RE: 21.11.2 patches review and test
Date: Fri, 29 Jul 2022 11:26:03 +0000	[thread overview]
Message-ID: <BYAPR11MB271182C7061B4720774344E4FE999@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BYAPR11MB2711E19AA2CCD1D3576884AEFE999@BYAPR11MB2711.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 5476 bytes --]

> -----Original Message-----
> From: Jiang, YuX
> Sent: Friday, July 29, 2022 11:01 AM
> To: Luca Boccassi <bluca@debian.org>; 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>; 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>; yanghliu@redhat.com
> Subject: RE: 21.11.2 patches review and test
> 
> > -----Original Message-----
> > From: Luca Boccassi <bluca@debian.org>
> > Sent: Thursday, July 28, 2022 8:34 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>; 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>; 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>; yanghliu@redhat.com
> > Subject: Re: 21.11.2 patches review and test
> >
> > On Mon, 2022-07-18 at 10:58 +0100, luca.boccassi@gmail.com wrote:
> > > Hi all,
> > >
> > > Here is a list of patches targeted for stable release 21.11.2.
> > >
> > > 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=v21.11.2-rc1
> > >
> > > These patches are located at branch 21.11 of dpdk-stable repo:
> > >     https://dpdk.org/browse/dpdk-stable/
> > >
> > > Thanks.
> > >
> > > Luca Boccassi
> >
> > Hello,
> >
> > Any update from any of the validation teams? Any indication on how the
> > tests are going?
> >
> > --
> > Kind regards,
> > Luca Boccassi
> 
> Everything is fine, find one vhost related issue which is investigated by Intel
> Dev.
> I will send a v1 report later. Thanks.
> 
> Best regards,
> Yu Jiang

Update the test status for Intel part. Till now dpdk21.11.2-rc1 test rate is 90%, no critical issue is found.
Failure defects as below:  
    Bug1: [dpdk v21.11.2-rc1] examples/performance-thread meson build error with gcc12.1 on fedora36
    Bug2: DPDK 21.11.1 cryptodev_qat_raw_api_autotest failing
        - Intel Dev send a patch to skip oop test for raw api, need be reviewed and merged.
    Bug3: [21.11LTS]Test with the new local patch, Vhost-user meet Segmentation fault issue when quit virtio-user before stopping sending packets
        - Intel Dev is under investigating.

# 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&22.04, Fedora36, RHEL8.4, etc.
  - All test done. Find one new defect as Bug1. 
* PF(i40e, ixgbe): test scenarios including RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc. 
  - Test rate is 90%. No new dpdk issue is found. 
* VF(i40e, ixgbe): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.		
  - Test rate is 90%. 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.
* Power: test scenarios including bi-direction/Telemetry/Empty Poll Lib/Priority Base Frequency, 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 one new issue, Intel Dev is under investigating.
      - Bug Summary:[21.11LTS]Test with the new local patch, Vhost-user meet Segmentation fault issue when quiting virtio-user before stopping sending packets
* Cryptodev: 
*Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
  - All test done. Only one defect as the above.
*Performance test: test scenarios including Thoughput Performance /Cryptodev Latency, etc.
  - All test done, no perf drop.

Best regards,
Yu Jiang

[-- Attachment #2: PATCH 21.11.1 v2 testcrypto skip oop test for raw api.msg --]
[-- Type: application/vnd.ms-outlook, Size: 108032 bytes --]

  reply	other threads:[~2022-07-29 11:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18  9:58 luca.boccassi
2022-07-19  2:40 ` Pei Zhang
2022-07-28 12:34 ` Luca Boccassi
2022-07-28 12:48   ` Ali Alnubani
2022-08-16  7:33     ` Ali Alnubani
2022-08-16 10:05       ` Luca Boccassi
2022-07-29  3:00   ` Jiang, YuX
2022-07-29 11:26     ` Jiang, YuX [this message]
2022-08-02 10:00       ` Luca Boccassi
2022-08-02 10:14         ` Jiang, YuX
2022-08-04  7:28           ` Jiang, YuX
2022-08-16 11:39             ` Luca Boccassi
2022-08-17 10:00               ` Jiang, YuX
2022-08-26  8:13                 ` Jiang, YuX
2022-08-26  9:06                   ` Kevin Traynor
2022-08-02  3:29   ` YangHang Liu
2022-08-02  9:32     ` Luca Boccassi
2022-08-29 13:00 ` Stokes, Ian
2022-08-29 16:20   ` Kevin Traynor

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=BYAPR11MB271182C7061B4720774344E4FE999@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=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).