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 23.11-rc2
Date: Thu, 9 Nov 2023 08:33:52 +0000	[thread overview]
Message-ID: <MW4PR11MB59124E5FEBFC29121824F2529FAFA@MW4PR11MB5912.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1746248.vCJZsxu672@thomas>

[-- Attachment #1: Type: text/plain, Size: 3641 bytes --]

> -----Original Message-----

> From: Thomas Monjalon <thomas@monjalon.net>

> Sent: Tuesday, November 7, 2023 6:22 AM

> To: announce@dpdk.org

> Subject: release candidate 23.11-rc2

>

> A new DPDK release candidate is ready for testing:

>            https://git.dpdk.org/dpdk/tag/?id=v23.11-rc2

>

> There are 320 new patches in this snapshot.

>

> Release notes:

>            https://doc.dpdk.org/guides/rel_notes/release_23_11.html

>

> Highlights of 23.11-rc2:

>            - RSS algorithm management

>            - maximum Rx buffer size

>            - nfp vDPA driver

>            - graph application

>

> There were a lot of updates in drivers.

> The driver features should be frozen now.

>

> Please test and report issues on bugs.dpdk.org.

>

> DPDK 23.11-rc3 is expected in approximately one week.

>

> Thank you everyone

>

Update the test status for Intel part. Till now dpdk23.11-rc2 test execution rate is 60%. found five new issues.



New issues:

1. ice dcf get vf resource failed when launch testpmd. -> Intel dev is under investigating

2. multiprocess_iavf/test_multiprocess_symmetric_mp_packet: Failed to start two processes. -> Intel dev is under investigating

3. https://bugs.dpdk.org/show_bug.cgi?id=1308 meson_tests/driver: link_bonding_rssconf_autotest test failed. -> not fix yet

4. DPDK 23.11-RC2 TSO Tests failing. -> Intel dev is under investigating

5. mev_cpfl_rte_flow/test_mac_ipv4_udp_encap_vxlan_io_to_vf: received incorrect packet. -> has fix patch



# 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 Ubuntu20.04.5, Ubuntu22.04.3, Fedora38, RHEL8.7/9.2, Centos7.9, OpenAnolis8.8, CBL-Mariner2.0 etc.

  - All test passed.

*Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu22.04.2 and RHEL9.0.

  - All test passed with latest dpdk.



* PF/VF(i40e, ixgbe, igc): test scenarios including PF/VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.

  - Execution rate is 90%. found 3 issues.

* PF/VF(ice): test scenarios including Switch features/Package Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Flexible Descriptor, etc.

  - Execution rate is 70%. found 1&2&3 issues.

* MEV test: test scenarios including PF/TSO/MTU/Jumboframe/checksum offload, etc

  - Execution rate is 90%. found 5 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 70%. 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 60%. No new issue is found.

* IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test - QAT&SW/FIB library, etc.

  - Execution rate is 50%. found 4 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.0, etc.

  - Execution rate is 70%. No new issue is found.

* Cryptodev:

 *Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.

  - on going. No new issue is found.

 *Performance test: test scenarios including Throughput Performance /Cryptodev Latency, etc.

  - on going. No new issue is found.





Regards,

Xu, Hailin

[-- Attachment #2: Type: text/html, Size: 8655 bytes --]

  reply	other threads:[~2023-11-09  8:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 22:22 Thomas Monjalon
2023-11-09  8:33 ` Xu, HailinX [this message]
2023-11-14  9:59   ` Xu, HailinX
2023-11-14 16:11 ` Thinh Tran

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=MW4PR11MB59124E5FEBFC29121824F2529FAFA@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).