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-rc2
Date: Thu, 6 Jul 2023 06:43:19 +0000	[thread overview]
Message-ID: <MW4PR11MB591285A0778AD669E5A750599F2CA@MW4PR11MB5912.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MW4PR11MB591214FE52746A80F73B94439F25A@MW4PR11MB5912.namprd11.prod.outlook.com>

> -----Original Message-----
> From: Xu, HailinX
> Sent: Thursday, June 29, 2023 2:50 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-rc2
> 
> > -----Original Message-----
> > From: Thomas Monjalon <thomas@monjalon.net>
> > Sent: Wednesday, June 28, 2023 9:00 AM
> > To: announce@dpdk.org
> > Subject: release candidate 23.07-rc2
> >
> > A new DPDK release candidate is ready for testing:
> > 	https://git.dpdk.org/dpdk/tag/?id=v23.07-rc2
> >
> > There are 237 new patches in this snapshot.
> >
> > Release notes:
> > 	https://doc.dpdk.org/guides/rel_notes/release_23_07.html
> >
> > There were a lot of updates in drivers.
> > The driver features should be frozen now.
> >
> > Please test and report issues on bugs.dpdk.org.
> > Do not forget to review examples, tests and documentation updates.
> > Breaking changes for 23.11 must be announced in 23.07.
> >
> > DPDK 23.07-rc3 is expected in approximately one week.
> >
> > Thank you everyone
> >
> Update the test status for Intel part. Till now dpdk23.07-rc2 test execution rate
> is 40%. 1 critical issue has been found.
> critical issues:
>     - https://bugs.dpdk.org/show_bug.cgi?id=1259 [dpdk-23.07] vf_smoke: vf
> cannot forward packets -> no fix yet # 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:
>     - [dpdk23.07][asan]
> multiprocess_iavf/multiprocess_simple_mpbasicoperation: AddressSanitizer:
> heap-use-after-free -> Intel dev is under investigating
>   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
> 	- 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
> * PF/VF(i40e, ixgbe): test scenarios including
> PF/VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
>   - Execution rate is 80%. Find 1 new bug(critical issues):
> * PF/VF(ice): test scenarios including Switch features/Package
> Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Flexible
> Descriptor, etc.
>   - Execution rate is 30%. 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.
>   - Execution rate is 60%. No new issue is found.
> * Power and IPsec:
>  * Power: test scenarios including bi-direction/Telemetry/Empty Poll
> Lib/Priority Base Frequency, etc.
>   - On going. 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.
>   - 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.
>   - On going. No new issue is found.
>  *Performance test: test scenarios including Throughput Performance
> /Cryptodev Latency, etc.
>   - On going. No performance drops.
> 
> Regards,
> Xu, Hailin

Update the test status for Intel part. Till now dpdk23.07-rc2 all tests done. 1 critical issue has been found.
critical issues:
    - https://bugs.dpdk.org/show_bug.cgi?id=1259 [dpdk-23.07] vf_smoke: vf cannot forward packets -> no fix yet
# 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:
      - [dpdk23.07][asan] multiprocess_iavf/multiprocess_simple_mpbasicoperation: AddressSanitizer: heap-use-after-free -> Intel dev is under investigating
      - [dpdk-23.07-rc2] Meson test is failing for some of the tests -> Intel dev is under investigating
    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
	  - 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
* 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(critical issues):
* 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 1 new bug:
      - [dpdk-23.07]dpdk-graph: dispatch mode can't receive and fwd pkts with large traffic -> have fix patch
* 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:
      - [dpdk-23.07-rc2] iavf 1c/2t avx512 performance drop 6% -> Intel dev is under investigating.
* 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. 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 done. Find 1 new bug:
      - [DPDK-23.07-rc2] l2fwd Crypto test is resulting in segmentation fault -> have fix patch
      - Gen3 SM4_ECB succeeding without legacy flag passed -> have fix patch
 *Performance test: test scenarios including Throughput Performance /Cryptodev Latency, etc.
  - All test done. No new issue is found.

Regards,
Xu, Hailin

  reply	other threads:[~2023-07-06  6:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28  0:59 Thomas Monjalon
2023-06-29  6:49 ` Xu, HailinX
2023-07-06  6:43   ` Xu, HailinX [this message]
2023-07-07  9:18 ` Thinh Tran

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