patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Xu, HailinX" <hailinx.xu@intel.com>
To: Xueming 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>,
	"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>,
	"Raslan Darawsheh" <rasland@nvidia.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Yanghang Liu <yanghliu@redhat.com>,
	"benjamin.walker@intel.com" <benjamin.walker@intel.com>,
	"qian.q.xu@intel.com" <qian.q.xu@intel.com>,
	"yuan.peng@intel.com" <yuan.peng@intel.com>,
	"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>
Subject: RE: 23.11.2 patches review and test
Date: Fri, 30 Aug 2024 10:00:41 +0000	[thread overview]
Message-ID: <MW4PR11MB5912292B7D0DB3E3A7B66C709F972@MW4PR11MB5912.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240822120634.525057-1-xuemingl@nvidia.com>


> -----Original Message-----
> From: Xueming Li <xuemingl@nvidia.com>
> Sent: Thursday, August 22, 2024 8:07 PM
> To: stable@dpdk.org
> Cc: dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.com>;
> Ali Alnubani <alialnu@nvidia.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>; Raslan
> Darawsheh <rasland@nvidia.com>; Thomas Monjalon
> <thomas@monjalon.net>; Yanghang Liu <yanghliu@redhat.com>;
> benjamin.walker@intel.com; qian.q.xu@intel.com; yuan.peng@intel.com;
> zhaoyan.chen@intel.com
> Subject: 23.11.2 patches review and test
> 
> Hi all,
> 
> Here is a list of patches targeted for stable release 23.11.2.
> 
> 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=v23.11.2-rc2
> 
> These patches are located at branch 23.11 of dpdk-stable repo:
>     https://dpdk.org/browse/dpdk-stable/
> 
> Thanks.
> 
> Xueming Li <xuemingl@nvidia.com>
Update the test status for Intel part. dpdk23.11.2-rc2 all validation test done. no new issue is found.

known issues:
  Failed to add vdev when launch dpdk-pdump with vdev secondary process
  start dpdk-pdump in VM with virtio-0.95 protocol failed
Note: fix patch has been merged into main, but they not merged 23.11.2, so this issue still exists in 23.11.2-rc2
Patch link: 
  https://patchwork.dpdk.org/project/dpdk/patch/20240314093630.1066948-2-mingjinx.ye@intel.com/
  https://patchwork.dpdk.org/project/dpdk/list/?series=30356&archive=both&state=*

# 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
  Ubuntu23.10, Ubuntu22.04, Fedora39, RHEL8.9, RHEL9.2, FreeBSD14.0, SUSE15, CentOS7.9, openEuler22.03-SP2,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. 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 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. No new dpdk issue is found.


Regards,
Xu, Hailin

  parent reply	other threads:[~2024-08-30 10:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22 12:06 Xueming Li
2024-08-28  7:23 ` YangHang Liu
2024-08-28  8:10   ` Xueming Li
2024-08-29  8:46 ` Ali Alnubani
2024-08-29 11:54   ` Xueming Li
2024-08-30 10:00 ` Xu, HailinX [this message]
2024-08-30 22:25   ` Xueming 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=MW4PR11MB5912292B7D0DB3E3A7B66C709F972@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=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).