From: "Jiang, YuX" <yux.jiang@intel.com>
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>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 21.05-rc3
Date: Tue, 18 May 2021 07:29:20 +0000 [thread overview]
Message-ID: <SJ0PR11MB5150CCDCA61FB58C3BF39FEEFE2C9@SJ0PR11MB5150.namprd11.prod.outlook.com> (raw)
In-Reply-To: <SJ0PR11MB5150A0722F73735F091F4B15FE509@SJ0PR11MB5150.namprd11.prod.outlook.com>
All,
Update the test status for Intel part. Till now dpdk21.05-rc3 test is almost finished and no critical issue blocked the test.
# 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, CentOS Stream 8, etc.
- All passed except "crypto_zuc build failed on Fedora34 with gcc 11". 3 patches have been provided to fix the gcc11 build issue and verified passed by validation team.
*Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu20.04 and CentOS Stream 8.
- All passed.
* PF(i40e, ixgbe and igb): test scenarios including RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
- All tests are done, find 1 new bug about unit_tests_power_cpufreq: unit test failed, Intel dev is investigating.
- 1 bug is reported based on rc1 in bugzilla. Patch has provided but need other patch supports, all of them will be fixed in next release.
> * https://bugs.dpdk.org/show_bug.cgi?id=687
* VF(i40e, ixgbe and igb): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
- All tests are done. No new issue is found.
* PF/VF(ICE): test scenarios including /Switch features/Package Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Share code update/Flexible Descriptor, etc.
- All tests are done. No new issue is found except known issues.
* Intel NIC single core/NIC performance: test scenarios including PF/VF single core performance test, RFC2544 Zero packet loss performance test, etc.
- All passed. No new issue is found.
* Power and IPsec:
* Power: test scenarios including bi-direction/Telemetry/Empty Poll Lib/Priority Base Frequency and so on.
- All passed. No new issue is found.
* IPsec: test scenarios including ipsec/ipsec-secgw
- All passed. 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 7.0u2, etc.
- All tests are done.
- No new issue is found except known issues which are found in rc2.
- 1 bug is reported based on rc2 in bugzilla. Patch has been provided and verified passed by validation team.
> * https://bugs.dpdk.org/show_bug.cgi?id=699
* Cryptodev:
*Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
- All tests are done. No new bug is found except known issue.
*Performance test: test scenarios including Thoughput Performance /Cryptodev Latency, etc.
- All tests are done. No big perf drop.
Best regards,
Yu Jiang
>-----Original Message-----
>From: Jiang, YuX
>Sent: Friday, May 14, 2021 6:07 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>
>Subject: RE: [dpdk-dev] [dpdk-announce] release candidate 21.05-rc3
>
>Update the test status for Intel part. Till now 70% is executed, 70% is
>debugged and no critical issue blocked the test.
>
># 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,
>CentOS Stream 8, etc.
> - All passed.
> *Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS
>such as Ubuntu20.04 and CentOS Stream 8.
> - All passed.
>
> * PF(i40e, ixgbe and igb): test scenarios including
>RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
> - Execution rate: 100%, debug rate: 80%.
> - Fixed RC2's critical bad commit id, issue DPDK PF+DPDK
>VF:launch testpmd failed by using VF, bugzilla688, bugzilla693.
> - 1 bug is reported in bugzilla still investigating.
> > * https://bugs.dpdk.org/show_bug.cgi?id=687
>
> * VF(i40e, ixgbe and igb): test scenarios including VF-
>RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
> - Execution rate: 100%, debug rate: 90%. No new issue is
>found.
>
> * PF/VF(ICE): test scenarios including /Switch features/Package
>Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Share
>code update/Flexible Descriptor, etc.
> - Execution rate: 80%, debug rate: 60%. No new issue is found.
> - 2 bugs about rss_pppoe add rss cfg failed and
>ip_fragment_pf_rss hash issues are found in RC2 have been fixed in RC3.
>
> * Intel NIC single core/NIC performance: test scenarios including
>PF/VF single core performance test, RFC2544 Zero packet loss performance
>test, etc.
> - Execution rate: 60%, debug rate: 60%. No new issue is found.
>
> * Power and IPsec:
> * Power: test scenarios including bi-
>direction/Telemetry/Empty Poll Lib/Priority Base Frequency and so on.
> - Execution rate: 90%, debug rate: 90%. No new issue
>is found.
> * IPsec: test scenarios including ipsec/ipsec-secgw, etc.
> - Under testing.
>
># 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.0u2, etc.
> - All tests are done. No new issue is found except known issue
>which is found in RC2.
> - 1 bug is reported in bugzilla still investigating.
> > * https://bugs.dpdk.org/show_bug.cgi?id=699
> * Cryptodev:
> *Function test: test scenarios including Cryptodev API
>testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
> - Execution rate: 100%, debug rate: 80%. No new bug
>is found execpt known issue.
> *Performance test: test scenarios including Thoughput
>Performance /Cryptodev Latency, etc.
> - Under testing.
>
>Best regards,
>Yu Jiang
>
>>-----Original Message-----
>>From: dev <dev-bounces@dpdk.org> On Behalf Of Thomas Monjalon
>>Sent: Thursday, May 13, 2021 4:57 AM
>>To: announce@dpdk.org
>>Subject: [dpdk-dev] [dpdk-announce] release candidate 21.05-rc3
>>
>>A new DPDK release candidate is ready for testing:
>> https://git.dpdk.org/dpdk/tag/?id=v21.05-rc3
>>
>>There are 114 new patches in this snapshot.
>>
>>Release notes:
>> https://doc.dpdk.org/guides/rel_notes/release_21_05.html
>>
>>Please test and report issues on bugs.dpdk.org.
>>You may share some release validation results by replying to this
>>message at dev@dpdk.org.
>>
>>DPDK 21.05-rc4 will be out during next week for the final touch.
>>
>>Thank you everyone
>>
next prev parent reply other threads:[~2021-05-18 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 20:57 Thomas Monjalon
2021-05-14 10:07 ` Jiang, YuX
2021-05-18 7:29 ` Jiang, YuX [this message]
2021-05-19 4:07 ` Thinh Tran
2021-05-19 10:45 ` Ali Alnubani
2021-05-20 7:34 ` Kalesh Anakkur Purayil
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=SJ0PR11MB5150CCDCA61FB58C3BF39FEEFE2C9@SJ0PR11MB5150.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=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).