DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Jiang, YuX" <yux.jiang@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	"dev (dev@dpdk.org)" <dev@dpdk.org>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
	"Devlin, Michelle" <michelle.devlin@intel.com>
Subject: RE: release candidate 22.07-rc1
Date: Wed, 15 Jun 2022 06:01:48 +0000	[thread overview]
Message-ID: <BYAPR11MB2711F8F22EBD6E71E0E0B79FFEAD9@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <2133922.NgBsaNRSFp@thomas>

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Thursday, June 9, 2022 4:51 AM
> To: announce@dpdk.org
> Subject: release candidate 22.07-rc1
>
> A new DPDK release candidate is ready for testing:
>       https://git.dpdk.org/dpdk/tag/?id=v22.07-rc1
>
> There are 576 new patches in this snapshot, constituting what the reviewers
> and maintainers were able to handle.
>
> Release notes:
>       https://doc.dpdk.org/guides/rel_notes/release_22_07.html
>
> Highlights of 22.07-rc1:
>       - initial RISC-V support
>       - sequence lock
>       - protocol-based metering
>       - Rx threshold event
>       - SFP telemetry
>       - async vhost improvements
>       - vhost library statistics
>       - vmxnet3 versions 5 & 6
>       - ECDH crypto
>       - DMA device telemetry
>       - SWX pipeline improvements
>       - integration as Meson subproject
>
> Please test and report issues on bugs.dpdk.org.
>
> DPDK 22.07-rc2 is expected in two weeks.
>
> Thank you everyone
>

Update the test status for Intel part. Till now dpdk22.07-rc1 test execution rate is 80%. No critical issue is found.

# 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, Ubuntu22.04, Fedora36, RHEL8.6 etc.
  - All test done. Find 1 new bug.
        - https://bugs.dpdk.org/show_bug.cgi?id=1016 [dpdk-22.07*] drivers/net/ice meson build failed with gcc12.1.1 on Fedora36/64
                Intel Dev is under investigating. No fix yet.
 *Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu22.04 and RHEL8.6.
  - All test done. Find 3 new bugs.
        - https://bugs.dpdk.org/show_bug.cgi?id=1032 [dpdk 22.07-rc1] app/test/test_cryptodev meson build failed with cflag param optimization=1 on Ubuntu22.04 &&RHEL8.6 with gcc11.2.0&&8.5.0
                Has fix, and verify passed
        - https://bugs.dpdk.org/show_bug.cgi?id=1033 [dpdk 22.07-rc1] app/test-flow-perf meson build failed with cflag param optimization=1 on Ubuntu22.04 &&RHEL8.6 with gcc11.2.0&&8.5.0
                Has fix, and verify passed
        - https://bugs.dpdk.org/show_bug.cgi?id=1029 [dpdk 22.07-rc1] drivers/net/cxgbe meson build failed with cflag param optimization=1 on Ubuntu22.04 &&RHEL8.6 with gcc11.2.0&&8.5.0
                Has fix, and verify passed

* PF/VF(i40e, ixgbe): test scenarios including PF/VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
        - Execution rate is 80%. Find 1 new issue: https://bugs.dpdk.org/show_bug.cgi?id=1028#c0, no fix yet.

* PF/VF(ice): test scenarios including Switch features/Package Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Flexible Descriptor, etc.
        - Execution rate is 80%. Find 4 new issues, Intel dev is under investigating.

* 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 80%.  No big performance drop.

* Power and IPsec:
 * Power: test scenarios including bi-direction/Telemetry/Empty Poll Lib/Priority Base Frequency, etc.
  - All test passed.
 * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test - QAT&SW/FIB library, etc.
        - Execution rate is 60%. Find 2 new issues, one has fix and verify passed. Other is https://bugs.dpdk.org/show_bug.cgi?id=1034, no fix yet.

# 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 7.0u3, etc.
        - Execution rate is 80%. Find 3 new bugs, Intel dev is under investigating.

* Cryptodev:
 *Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
        - Execution rate is 80%. No new issue is found
 *Performance test: test scenarios including Throughput Performance /Cryptodev Latency, etc.
        - Execution rate is 80%.  No new issue is found.

Best regards,
Yu Jiang

  reply	other threads:[~2022-06-15  6:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 20:51 Thomas Monjalon
2022-06-15  6:01 ` Jiang, YuX [this message]
2022-06-16  8:29   ` Jiang, YuX
2022-06-16 13:11 ` Wael Abualrub

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=BYAPR11MB2711F8F22EBD6E71E0E0B79FFEAD9@BYAPR11MB2711.namprd11.prod.outlook.com \
    --to=yux.jiang@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=michelle.devlin@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).