DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xu, HailinX" <hailinx.xu@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, "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 25.03-rc2
Date: Tue, 18 Mar 2025 09:44:51 +0000	[thread overview]
Message-ID: <MW4PR11MB5912C7B4E1F37937781195459FDE2@MW4PR11MB5912.namprd11.prod.outlook.com> (raw)
In-Reply-To: <4098448.yKrmzQ4Hd0@thomas>

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Friday, March 7, 2025 1:42 AM
> To: announce@dpdk.org
> Subject: release candidate 25.03-rc2
> 
> A new DPDK release candidate is ready for testing:
> 	https://git.dpdk.org/dpdk/tag/?id=v25.03-rc2
> 
> There are 251 new patches in this snapshot.
> 
> Release notes:
> 	https://doc.dpdk.org/guides/rel_notes/release_25_03.html
> 
> Most significant changes are in multiple drivers.
> 
> Please test and report new issues on https://bugs.dpdk.org
> 
> DPDK 25.03-rc3 is expected in one week.
> As it is a small release, we may try to close this cycle in advance.
> 
> Thank you everyone
> 
Update the test status for Intel part. dpdk25.03-rc2 all test is done. found eight new issues and not found 

New issues:
1. Bug 1671-loopback_virtio_user_server_mode: failed to launch dpdk-pdump	-- not fix yet
2. pf_smoke:pf_jumbo_frames: max mtu tx error for E810		-- Intel dev is under investigating                 
3. unit_tests_cryptodev_func/cryptodev_qat_raw_api_autotest: test failing	-- Intel dev is under investigating
4. Bug 1672-vf_offload/checksum_offload_tunnel_enable: gtpu packet checksum error packet		-- -- not fix yet
5. [mev] cpfl_vf_representor_rte_flow/port_representor_probe_scan: port attach failed		-- Intel dev is under investigating
6. loopback_multi_paths_port_restart: core dumped occurred when exiting testpmd		-- Intel dev is under investigating
7. vhost_virtio_fuzzing/tso_forward_pkt: addressSanitizer error occurred when exiting testpmd		-- Intel dev is under investigating
8. PtpClient: time synchronous error		-- 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 Ubuntu24.10, Ubuntu24.04.1, Fedora41, RHEL10, RHEL9.4, RHEL9.5-RT, FreeBSD14.2, SUSE15.6, OpenAnolis8.9, AzureLinux3.0 etc.
  - All test passed.
 *Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu24.04.1 and RHEL9.4.
  - All test passed with latest dpdk.
* PF/VF(i40e, ixgbe, igb&igc): test scenarios including PF/VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc. 
	- All test case is done. found the 6 issue.
* PF/VF(ice): test scenarios including Switch features/Package Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Flexible Descriptor, etc.
	- Execution rate is done. found the 2,4,6 issues.
* PF/VF(apfi/cpfi): test scenarios including cpfi_rte_flow/TSO/MTU/Jumboframe/checksum offload, etc.
	- Execution rate is done. found the 5 issues.
* 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 done. 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 done. No new issue is found.
 * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test - QAT&SW/FIB library, etc.
	- Execution rate is 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.0U1, etc.
	- Execution rate is done. found the 1,3 issues.
* Cryptodev: 
 *Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
	- Execution rate is done. No new issue is found.
 *Performance test: test scenarios including Throughput Performance /Cryptodev Latency, etc.
	- Execution rate is done. No performance drop.

Regards,
Xu, Hailin

      parent reply	other threads:[~2025-03-18  9:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06 17:42 Thomas Monjalon
2025-03-14 19:26 ` Thinh Tran
2025-03-18  9:44 ` 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=MW4PR11MB5912C7B4E1F37937781195459FDE2@MW4PR11MB5912.namprd11.prod.outlook.com \
    --to=hailinx.xu@intel.com \
    --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).