DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xu, HailinX" <hailinx.xu@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	"announce@dpdk.org" <announce@dpdk.org>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Kovacevic, Marko" <marko.kovacevic@intel.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	Ferruh Yigit <ferruh.yigit@xilinx.com>
Subject: RE: release candidate 23.07-rc1
Date: Wed, 21 Jun 2023 05:30:38 +0000	[thread overview]
Message-ID: <SA1PR11MB592475AA087D4CBB9230DACB9F5DA@SA1PR11MB5924.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MW4PR11MB59127A8D458BA869E71322859F5BA@MW4PR11MB5912.namprd11.prod.outlook.com>

> -----Original Message-----
> From: Xu, HailinX
> Sent: Thursday, June 15, 2023 3:18 PM
> To: Thomas Monjalon <thomas@monjalon.net>; announce@dpdk.org;
> dev@dpdk.org
> Cc: Kovacevic, Marko <Marko.Kovacevic@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>; Richardson, Bruce
> <bruce.richardson@intel.com>; Ferruh Yigit <ferruh.yigit@xilinx.com>
> Subject: RE: release candidate 23.07-rc1
> 
> > -----Original Message-----
> > From: Thomas Monjalon <thomas@monjalon.net>
> > Sent: Tuesday, June 13, 2023 5:39 AM
> > To: announce@dpdk.org
> > Subject: release candidate 23.07-rc1
> >
> > A new DPDK release candidate is ready for testing:
> > 	https://git.dpdk.org/dpdk/tag/?id=v23.07-rc1
> >
> > There are 574 new patches in this snapshot.
> >
> > Release notes:
> > 	https://doc.dpdk.org/guides/rel_notes/release_23_07.html
> >
> > Highlights of 23.07-rc1:
> > 	- AMD CDX bus
> > 	- PCI MMIO read/write
> > 	- new flow patterns: Tx queue, Infiniband BTH
> > 	- new flow actions: push/remove IPv6 extension
> > 	- indirect flow rule list
> > 	- flow rule update
> > 	- vhost interrupt callback
> > 	- VDUSE in vhost library
> > 	- more ShangMi crypto algorithms
> > 	- PDCP library
> > 	- removed LiquidIO driver
> >
> > Please test and report issues on bugs.dpdk.org.
> >
> > DPDK 23.07-rc2 is expected in approximately two weeks.
> >
> > This release candidate comes late, maintainers need more help.
> > Renewing the maintainers staff and getting more reviews are topics
> > under discussion in the techboard meetings.
> > 	https://core.dpdk.org/techboard/minutes/
> >
> > Thank you everyone
> 
> Update the test status for Intel part. Till now dpdk23.07-rc1 test execution rate
> is 50%. 2 critical issues have been found.
> critical issues:
>     1. [dpdk-23.07] ice_switch_filter/test_mac_ipv4_tcp_pipeline_mode:
> Failed to create rule -> Intel dev is under investigating
>     2. [dpdk-23.07] no probed ethernet devices after starting testpmd with
> ICX-D -> Intel dev is under investigating # Basic Intel(R) NIC testing
> * Build or compile:
>  *Build: cover the build test combination with latest GCC/Clang version and
> the popular OS revision such as Ubuntu20.04.5, Ubuntu22.04.2, Fedora38,
> RHEL8.7/9.2, Centos7.9, OpenAnolis8.8, CBL-Mariner2.0 etc.
>   - All test passed.
>  *Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as
> Ubuntu22.04.2 and RHEL9.0.
>   - All test passed with latest dpdk.
> * Meson test & Asan test:
>     known issue:
> 	    - https://bugs.dpdk.org/show_bug.cgi?id=1107 [22.11-rc1][meson
> test] seqlock_autotest test failed
> 	    - https://bugs.dpdk.org/show_bug.cgi?id=1123 [dpdk-22.11][asan]
> the stack-buffer-overflow was found when quit testpmd in Redhat9
> * PF/VF(i40e, ixgbe): test scenarios including
> PF/VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
> 	- Execution rate is 90%. Find 1 new bug:
>         https://bugs.dpdk.org/show_bug.cgi?id=1249: [dpdk-23.07] ixgbe
> port stop failed after launch testpmd -> No fix yet
> * PF/VF(ice): test scenarios including Switch features/Package
> Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Flexible
> Descriptor, etc.
> 	- Execution rate is 50%. Find 2 new bugs: critical issues 1&2
> * Intel NIC single core/NIC performance: test scenarios including PF/VF single
> core performance test, RFC2544 Zero packet loss performance test, etc.
> 	- Execution rate is 50%. No new issue is found
> * Power and IPsec:
>  * Power: test scenarios including bi-direction/Telemetry/Empty Poll
> Lib/Priority Base Frequency, etc.
> 	- Execution rate is 50%. No new issue is found.
>  * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test -
> QAT&SW/FIB library, etc.
> 	- On going. No new 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.
> 	- Execution rate is 80%. Find 1 new issue:
>         [dpdk-23.07] start dpdk-pdump in VM with virtio-0.95 protocol failed ->
> Intel dev is under investigating
> * Cryptodev:
>  *Function test: test scenarios including Cryptodev API testing/CompressDev
> ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
> 	- On going. No new issue is found.
>  *Performance test: test scenarios including Throughput Performance
> /Cryptodev Latency, etc.
> 	- On going. No performance drop.
> 
> 
> Regards,
> Xu, Hailin
> >

Update the test status for Intel part. Till now dpdk23.07-rc1 all tests done. 3 critical issues have been found.
critical issues:
    1. [dpdk-23.07] ice_switch_filter/test_mac_ipv4_tcp_pipeline_mode: Failed to create rule -> has fix patch
    2. [dpdk-23.07] no probed ethernet devices after starting testpmd with ICX-D -> has fix patch
    3. [dpdk-23.07] WIN: CVL DDP init error and Segmentation fault on Windows -> Intel dev is under investigating
# Basic Intel(R) NIC testing
* Build or compile:  
 *Build: cover the build test combination with latest GCC/Clang version and the popular OS revision such as Ubuntu20.04.5, Ubuntu22.04.2, Fedora38, RHEL8.7/9.2, Centos7.9, OpenAnolis8.8, CBL-Mariner2.0 etc.
  - All test passed.
 *Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu22.04.2 and RHEL9.0.
  - All test passed with latest dpdk.
* Meson test & Asan test: 
    new issue:
        - https://bugs.dpdk.org/show_bug.cgi?id=1250 [dpdk-23.07][meson test] driver-tests/cryptodev_openssl_asym_autotest blocked in RHEL9.0 -> no fix yet
    known issue:
	- https://bugs.dpdk.org/show_bug.cgi?id=1107 [22.11-rc1][meson test] seqlock_autotest test failed
	- https://bugs.dpdk.org/show_bug.cgi?id=1123 [dpdk-22.11][asan] the stack-buffer-overflow was found when quit testpmd in Redhat9
* PF/VF(i40e, ixgbe): test scenarios including PF/VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc. 
  - All test done. Find 1 new bug: 
        - https://bugs.dpdk.org/show_bug.cgi?id=1249: [dpdk-23.07] ixgbe port stop failed after launch testpmd -> has fix patch
* PF/VF(ice): test scenarios including Switch features/Package Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Flexible Descriptor, etc.
  - All test done. Find 6 new bugs: critical issues 1&2
        - kernelpf_iavf/iavf_dual_vlan_insert: The behavior of vector and scalar on vlan insert is inconsistent -> has fix patch
        - [dpdk-23.07]The SCTP tunnel packet of iavf cannot be forwarded in avx2 mode -> has fix patch
        - [dpdk-23.07]large_vf/multi_vfs_256_queues:"OP_DEL_RSS_INPUT_CFG" error appears when starting testpmd -> Intel dev is under investigating
        - https://bugs.dpdk.org/show_bug.cgi?id=1253 [dpdk-23.07] vf_offload/test_tso_tunnel: IPv6/UDP/GTPU packet of iavf cannot be forwarded in 32bit -> no fix yet
* 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. find 1 new bug: 
        - https://bugs.dpdk.org/show_bug.cgi?id=1254 [dpdk-23.07] iavf performance drop 8% -> no fix yet
* Power and IPsec: 
 * Power: test scenarios including bi-direction/Telemetry/Empty Poll Lib/Priority Base Frequency, etc. 
  - All test done. No new issue is found. 
 * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test - QAT&SW/FIB library, etc.
  - All test done. No new 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. Find 3 new issues:
        - [dpdk-23.07]quit dpdk-ntb APP will print 'EAL: Error disabling MSI-X interrupts for fd 39' info -> has fix patch
        - [dpdk-23.07]start dpdk-pdump in VM with virtio-0.95 protocol failed -> Intel dev is under investigating
        - [dpdk-23.07]vm2vm_virtio_net_perf: iperf will drop to 0 start vhost-user and QEMU with multi-queues and TSO disabled -> Intel dev is under investigating
* Cryptodev: 
 *Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
  - All test done. No new issue is found.
 *Performance test: test scenarios including Throughput Performance /Cryptodev Latency, etc.
  - All test done. No performance drops.

Regards,
Xu, Hailin


      reply	other threads:[~2023-06-21  5:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 21:38 Thomas Monjalon
2023-06-15  7:17 ` Xu, HailinX
2023-06-21  5:30   ` Xu, HailinX [this message]

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=SA1PR11MB592475AA087D4CBB9230DACB9F5DA@SA1PR11MB5924.namprd11.prod.outlook.com \
    --to=hailinx.xu@intel.com \
    --cc=announce@dpdk.org \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@xilinx.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=thomas@monjalon.net \
    /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).