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>,
"Puttaswamy, Rajesh T" <rajesh.t.puttaswamy@intel.com>,
"Cui, KaixinX" <kaixinx.cui@intel.com>
Subject: Test report for 24.03-rc2
Date: Fri, 15 Mar 2024 08:46:49 +0000 [thread overview]
Message-ID: <MW4PR11MB591233B92D036DDA5421DF3C9F282@MW4PR11MB5912.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3061 bytes --]
Update the test status for Intel part. dpdk24.03-rc2 all test is done. found five new issues.
New issues:
1. loopback_virtio_user_server_mode: Failed to add vdev when launch dpdk-pdump -> has fix patch
2. DMA devices stats not reset after API testsuite -> has fix patch
3. https://bugs.dpdk.org/show_bug.cgi?id=1398 ptpclient causes NIC I225/I226 port RX missed -> has fix patch
4. meson_test/test_fasts: eal_flags_file_prefix_autotest and eal_flags_b_opt_autotest failed -> has fix patch
5. mdd_failure_diagnose/test_malicious_packet_segment_size: Failed to check size of mbuf segment on PF -> 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 Ubuntu23.10, Ubuntu22.04.3, Fedora39, RHEL8.9/9.2, Centos7.9, FreeBSD14.0, SUSE15, OpenAnolis8.8, CBL-Mariner2.0 etc.
- All test passed.
*Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu22.04.3 and RHEL9.2.
- 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 fourth issue.
* PF/VF(igc): test scenarios including PF/VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
- All test case is done. found the third 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 fourth and fifth 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; IPsec; DLB; DSA dmadev:
* 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.
* DLB: test scenarios including DLB2/DLB2.5
- Execution rate is done. No new issue is found.
* DSA dmadev: - Execution rate is done. found the second 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. found the first 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
[-- Attachment #2: Type: text/html, Size: 7432 bytes --]
reply other threads:[~2024-03-15 8:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=MW4PR11MB591233B92D036DDA5421DF3C9F282@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=kaixinx.cui@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=rajesh.t.puttaswamy@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).