From: "Xu, HailinX" <hailinx.xu@intel.com>
To: "Marchand, David" <david.marchand@redhat.com>,
"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>,
"Puttaswamy, Rajesh T" <rajesh.t.puttaswamy@intel.com>
Subject: RE: release candidate 24.07-rc2
Date: Tue, 23 Jul 2024 02:14:05 +0000 [thread overview]
Message-ID: <MW4PR11MB5912E94C363ACD8EFC22D20E9FA92@MW4PR11MB5912.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8yPESOEVHydQWUnhcY+dYQN8y2V5sPwdLE6WGQVJKjytw@mail.gmail.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Saturday, July 13, 2024 2:25 AM
> To: announce@dpdk.org
> Cc: Thomas Monjalon <thomas@monjalon.net>
> Subject: release candidate 24.07-rc2
>
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v24.07-rc2
>
> There are 461 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_24_07.html
>
> Highlights of 24.07-rc2:
> - SVE support in the hash library
> - FEC support in net/i40e and net/ice
> - log cleanups in drivers
> - various driver fixes and updates
>
> Please test and report issues on bugs.dpdk.org.
>
> DPDK 24.07-rc3 is expected in approximately one week.
>
> Thank you everyone
>
> --
> David Marchand
Update the test status for Intel part. dpdk24.07-rc2 all test is done. found four new issues.
New issues:
1. Bug 1497 - [dpdk-24.07] [ABI][meson test] driver-tests/event_dma_adapter_autotest test hang when do ABI testing -> not fix yet
2. ipsec-secgw tests fail -> Intel dev is under investigating
3. ice_rx_timestamp/single_queue_with_timestamp: obtained unexpected timestamp -> Intel dev is under investigating
4. cryptodev_cpu_aesni_mb_autotest is failing -> 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 Ubuntu22.04.4, Ubuntu24.04, Fedora40, RHEL9.3, RHEL9.4, FreeBSD14.0, SUSE15.5, OpenAnolis8.8, CBL-Mariner2.0 etc.
- All test passed.
*Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu24..04 and RHEL9.4.
- 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. No new issue is found.
* 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 3 issue.
* 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. found the 2 issue.
# 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. No new issue is found.
* Cryptodev:
*Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
- Execution rate is done. found the 4 issue.
*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:[~2024-07-23 2:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 18:25 David Marchand
2024-07-17 22:31 ` Thinh Tran
2024-07-23 2:14 ` 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=MW4PR11MB5912E94C363ACD8EFC22D20E9FA92@MW4PR11MB5912.namprd11.prod.outlook.com \
--to=hailinx.xu@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@xilinx.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=rajesh.t.puttaswamy@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).