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 24.11-rc2
Date: Wed, 20 Nov 2024 02:54:46 +0000 [thread overview]
Message-ID: <MW4PR11MB5912DE5BEF00F44A3423C89A9F212@MW4PR11MB5912.namprd11.prod.outlook.com> (raw)
In-Reply-To: <13189755.ag9G3TJQzC@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Tuesday, November 12, 2024 11:24 PM
> To: announce@dpdk.org
> Subject: release candidate 24.11-rc2
>
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v24.11-rc2
>
> There are 444 new patches in this snapshot, including some library features
> and new drivers.
> It is becoming a big release.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_24_11.html
>
> Highlights of 24.11-rc2:
> - lcore variables allocation
> - AMD uncore power management
> - per-CPU power management QoS for resume latency
> - logging rework (timestamp, color, syslog, journal)
> - RSS hash key generation
> - ZTE zxdh net driver initialization
> - Napatech ntnic flow engine
>
> Please test and report issues on bugs.dpdk.org.
>
> We are very late in the schedule.
> DPDK 24.11-rc3 must appear on the next Tuesday 19, in order to allow an -rc4
> before closing the release on Friday, November 29.
>
> Thank you everyone
>
Update the test status for Intel part. dpdk24.11-rc2 all test is done. found six new issues.
New issues:
1. [dpdk-24.11] ice_enable_basic_hqos_on_pf: failed to load level topology from ddp -> Intel dev is under investigating
2. [dpdk-24.11]Linkville pmd_bonded_8023ad/command_line_option: set lacp failed -> Intel dev is under investigating
3. https://bugs.dpdk.org/show_bug.cgi?id=1579 - [dpdk-24.11-rc2] meson_tests/fasts malloc_autotest test failed on i40e -> not fix yet
4. [dpdk-24.11] [CNV] meson_tests/perf: hash_readwrite_lf_perf_autotest test timeout -> Intel dev is under investigating
5. https://bugs.dpdk.org/show_bug.cgi?id=1576 - [dpdk24.11-rc2] DPDK build failed with EXTRA_CFLAGS='-O1' on Redhat9.4 -> not fix yet
6. [dpdk24.11][CNV200G] start and quit testpmd cause link to stay down -> 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, Fedora40, RHEL8.10 RHEL9.4, FreeBSD14.1, SUSE15.6, OpenAnolis8.9, AzureLinux 3.0 etc.
- Execution rate is done. found the 5 issue.
*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): test scenarios including PF/VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
- All test case is done. found the 2&3 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 1&4&6 issue.
* CPF/APF(MEV): test scenarios including APF-HOST,CPF-HOST,CPF-ACC,cpfl_rte_flow/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. 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. 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:[~2024-11-20 2:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 15:23 Thomas Monjalon
2024-11-20 2:54 ` 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=MW4PR11MB5912DE5BEF00F44A3423C89A9F212@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).