From: "Jiang, YuX" <yux.jiang@intel.com>
To: "Jiang, YuX" <yux.jiang@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
"dev (dev@dpdk.org)" <dev@dpdk.org>
Cc: "Devlin, Michelle" <michelle.devlin@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Sun, QingX" <qingx.sun@intel.com>
Subject: RE: release candidate 22.03-rc2
Date: Thu, 3 Mar 2022 04:13:00 +0000 [thread overview]
Message-ID: <BYAPR11MB27114A308281871E489AC1E3FE049@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BYAPR11MB2711A2C3F4B28D14BE982D9EFE029@BYAPR11MB2711.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Jiang, YuX <yux.jiang@intel.com>
> Sent: Tuesday, March 1, 2022 6:57 PM
> To: Thomas Monjalon <thomas@monjalon.net>; dev (dev@dpdk.org)
> <dev@dpdk.org>
> Cc: Devlin, Michelle <michelle.devlin@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>; Sun,
> QingX <qingx.sun@intel.com>
> Subject: RE: release candidate 22.03-rc2
>
> > -----Original Message-----
> > From: Thomas Monjalon <thomas@monjalon.net>
> > Sent: Monday, February 28, 2022 5:02 AM
> > To: announce@dpdk.org
> > Subject: release candidate 22.03-rc2
> >
> > A new DPDK release candidate is ready for testing:
> > https://git.dpdk.org/dpdk/tag/?id=v22.03-rc2
> >
> > There are 306 new patches in this snapshot.
> >
> > Release notes:
> > https://doc.dpdk.org/guides/rel_notes/release_22_03.html
> >
> > Highlights of 22.03-rc2:
> > - ethdev flow API for templates and async operations
> > - Marvell GPIO driver for CNXK
> >
> > The driver features should be frozen now.
> > Please test and report issues on bugs.dpdk.org.
> >
> > DPDK 22.03-rc3 is expected in one week.
> >
> > Thank you everyone
> >
Update the test status for Intel part. Till now dpdk22.03-rc2 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/ICC version and the popular OS revision such as Ubuntu20.04, Fedora35, RHEL8.4, RHEL8.5 etc.
- All test passed.
- One known issue https://bugs.dpdk.org/show_bug.cgi?id=928, use "meson setup -Ddisable_drivers=event/cnxk" to build.
*Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu20.04 and RHEL8.4.
- All test done.
- One new bug https://bugs.dpdk.org/show_bug.cgi?id=939 is found.
> Rakesh Kudurumalla provides a patch, but we verify failed with gcc10.3.0+kernel-5.8.0-48-generic on Ubuntu20.04.
* PF(i40e, ixgbe): test scenarios including RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
- Execution rate is 80%. One new bug https://bugs.dpdk.org/show_bug.cgi?id=944 is found.
* VF(i40e, ixgbe): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
- Execution rate is 80%.
- One new bug about "vf_daemon/vf_mtu: VF setting MTU in DPDK then send one packet ,VF0 can't receive and transmit packet", Intel dev is investigating.
* PF/VF(ice): test scenarios including Switch features/Package Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Flexible Descriptor, etc.
- Execution rate is 90%.
- One new bug about "https://bugs.dpdk.org/show_bug.cgi?id=941 [dpdk-22.03] core dump when create fdir rule with bad arguments" is found.
> It has been fixed by patch https://patchwork.dpdk.org/project/dpdk/patch/20220301224739.3072563-1-akozyrev@nvidia.com/
* Intel NIC single core/NIC performance: test scenarios including PF/VF single core performance test, RFC2544 Zero packet loss performance test, etc.
- All test passed. 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.
- All test done.
- One new bug about "Failure with testing crypto -ipsec-secgw with AUTH-GMAC" is found.
> It has fix: https://patches.dpdk.org/project/dpdk/patch/20220301134133.1886839-1-radu.nicolau@intel.com/
# 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.
- All test done. One new bug https://bugs.dpdk.org/show_bug.cgi?id=940 is found.
* Cryptodev:
*Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
- Execution rate is 20%. One new bug about "Failed to run cryptodev_qat_asym_autotest" is found. Intel dev is investigating.
*Performance test: test scenarios including Thoughput Performance /Cryptodev Latency, etc.
- Execution rate is 20%.
BRs
Yu Jiang
next prev parent reply other threads:[~2022-03-03 4:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 21:02 Thomas Monjalon
2022-03-01 10:56 ` Jiang, YuX
2022-03-01 12:35 ` Thomas Monjalon
2022-03-01 14:41 ` Alexander Kozyrev
2022-03-03 4:13 ` Jiang, YuX [this message]
2022-03-04 12:03 ` Jiang, YuX
2022-03-03 17:54 ` Thinh Tran
2022-03-07 13:55 ` Pei Zhang
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=BYAPR11MB27114A308281871E489AC1E3FE049@BYAPR11MB2711.namprd11.prod.outlook.com \
--to=yux.jiang@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=michelle.devlin@intel.com \
--cc=qingx.sun@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).