From: "Xu, HailinX" <hailinx.xu@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
Ferruh Yigit <ferruh.yigit@xilinx.com>
Subject: RE: release candidate 25.07-rc1
Date: Thu, 26 Jun 2025 09:31:30 +0000 [thread overview]
Message-ID: <DS4PPF00BBED10C0A1937CEE1A0947261909F7AA@DS4PPF00BBED10C.namprd11.prod.outlook.com> (raw)
In-Reply-To: <5554581.qSoW2BAyJ8@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Thursday, June 12, 2025 9:57 AM
> To: announce@dpdk.org
> Subject: release candidate 25.07-rc1
>
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v25.07-rc1
>
> There are 542 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_25_07.html
>
> Highlights of 25.07-rc1:
> - Mucse RNP driver
> - ZTE Storage Data Accelerator (ZSDA) crypto driver
> - Performance Monitoring Unit (PMU) library
> - mempool optimization
> - zeroing of sensitive memory
> - RSS type for RoCE v2
> - graph feature arc and nodes for FIB
> - eventdev vector adapter
> - argparse enhanced
> - more libraries enabled with Windows MSVC
> - export symbols with macros instead of .map file
>
> Please test and report issues on bugs.dpdk.org.
>
> DPDK 25.07-rc2 is expected in two weeks.
>
> Thank you everyone
>
Update the test status for Intel part. dpdk25.07-rc1 all test is done. found three new issues.
New issues:
1. [dpdk-25.07] generic_flow_api/fdir_for_ipv4: the match rule packet cannot match the rule -> Intel dev is under investigating
2. [dpdk-25.07] DCF RSS hash update failed -> has fix patch
3. [dpdk-25.07] virtio_ipsec_cryptodev_func/test_aesni_mb_aes_cbc_sha1_hmac & test_virtio_aes_cbc_sha1_hmac: both test failed -> 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 Ubuntu25.04, Ubuntu24.04.2, Fedora42, RHEL10, RHEL9.6, RHEL9.6-RT, FreeBSD14.2, SUSE15.6, OpenAnolis8.10, AzureLinux3.0 etc.
- All test passed.
*Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu24.04.2 and RHEL9.6.
- All test passed with latest dpdk.
* PF/VF(i40e, ixgbe): test scenarios including PF/VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
- All test case is done. found the 1 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 issue.
* PF/VF(apfi/cpfi): test scenarios including cpfi_rte_flow/TSO/MTU/Jumboframe/checksum offload, etc.
- Execution rate is done. 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 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 3 issue.
* 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
prev parent reply other threads:[~2025-06-26 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 1:56 Thomas Monjalon
2025-06-20 20:46 ` Thinh Tran
2025-06-26 9:31 ` 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=DS4PPF00BBED10C0A1937CEE1A0947261909F7AA@DS4PPF00BBED10C.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=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).