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: "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-rc1
Date: Thu, 29 Apr 2021 07:36:27 +0000	[thread overview]
Message-ID: <SJ0PR11MB51502A2AC546E7561F331192FE5F9@SJ0PR11MB5150.namprd11.prod.outlook.com> (raw)
In-Reply-To: <SJ0PR11MB5150FBBD484FF001E92FC873FE439@SJ0PR11MB5150.namprd11.prod.outlook.com>

All,

Update the test status for Intel part. Till now dpdk21.05-rc1 test is almost finished and no critical issue.

# 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.
- All tests are done.
- 7 new bugs are found,
> 3 bugs are reported in bugzilla:
* https://bugs.dpdk.org/show_bug.cgi?id=687
* https://bugs.dpdk.org/show_bug.cgi?id=688  (Nvidia Dev. has provided patch, Intel member is verifying it.)
* https://bugs.dpdk.org/show_bug.cgi?id=693
> Other bugs are about csum fwd mode can not transmit packet, i40e ddp_gtp flow_director_filter take no effect, etc. Intel Dev. are working on them, have fixed 1 bug currently.

* 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 except known issue.

* 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.
- 7 new bugs are found about QinQ&DCF&GTPOGRE issues, Others are known issues. Intel Dev. are working on them, have fixed 2 bugs currently.

* Intel NIC single core/NIC performance: test scenarios including PF/VF single core performance test, RFC2544 Zero packet loss performance test, etc.
- All tests are done.
- 1 new issue is found about perf drops about 20% when use iavf to test multi-queue single core performance. Intel Dev. has provided patch to fix it, patch is awaiting upstream.

* Power and IPsec:
* Power: test scenarios including bi-direction/Telemetry/Empty Poll Lib/Priority Base Frequency and so on.
 - All tests are done.
- 1 new issue is found about launch dpdk-l3fwd-power failed. Intel Dev. are working on it and has provide patch to fix it.
 * IPsec: test scenarios including ipsec/ipsec-secgw
- 1 new issue is found about ipsec-secgw test failed. Problematic commit-id "9a1cc8f1ed examples/ipsec-secgw: support UDP encapsulation" from marvell.

# 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.

* Cryptodev:
*Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
- All tests are done. No new issue 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,
Jiang, Yu

-----Original Message-----
From: Jiang, YuX
Sent: Sunday, April 25, 2021 7:05 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-rc1

All,

Update the test status for Intel part. Till now 80% is executed, 80% is debuged 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%.
- 5 new bugs are found,
> 2 bugs are reported in bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=688  & https://bugs.dpdk.org/show_bug.cgi?id=687
> Other bugs are about csum fwd mode can not transmit packet, i40e ddp_ gtp flow_director_filter take no effect, etc. Intel Dev. are working on them.

* VF(i40e, ixgbe and igb): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
- Execution rate: 100%, debug rate: 80%. No new issue is found except known issue.

* 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: 90%, debug rate: 70%.
- 3 new bugs are found about QinQ&DCF issues, Others are known issues.

* Intel NIC single core/NIC performance: test scenarios including PF/VF single core performance test, RFC2544 Zero packet loss performance test, etc.
- Execution rate: 70%, debug rate: 70%. 1 new issue is found about perf drops about 20% when use iavf to test multi-queue single core performance. Intel Dev. are working on them.

* Power and IPsec:
* Power: test scenarios including bi-direction/Telemetry/Empty Poll Lib/Priority Base Frequency and so on.
 - Execution rate: 100%, debug rate: 70%. 2 issues are under debugging, Intel member is working on them.
 * IPsec: Not test 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.0u2, etc.
- Execution rate: 80%, debug rate: 80%. No new issue is found currently, except known issue.

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

Best regards,
Jiang, Yu

-----Original Message-----
From: dev <dev-bounces@dpdk.org> On Behalf Of Thomas Monjalon
Sent: Thursday, April 22, 2021 7:02 AM
To: announce@dpdk.org
Subject: [dpdk-dev] [dpdk-announce] release candidate 21.05-rc1

A new DPDK release candidate is ready for testing:
https://git.dpdk.org/dpdk/tag/?id=v21.05-rc1

There are 879 new patches in this snapshot.

Release notes:
https://doc.dpdk.org/guides/rel_notes/release_21_05.html

Highlights of 21.05-rc1, grouped by category:
* General
- Alpine Linux support
- mass renaming of lib directories
- allow disabling some libraries
- log names alignment and help command
- phase-fair lock
- Marvell CN10K SoC support
* Networking
- predictable RSS
- port representor syntax for sub-function and multi-host
- packet integrity in flow rule matching
- metering using flow actions
- TCP connection tracking offload
- Windows support of ice, pcap and vmxnet3 drivers

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

DPDK 21.05-rc2 is expected in two weeks.

Thank you everyone



  reply	other threads:[~2021-04-29  7:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 23:01 Thomas Monjalon
2021-04-25 11:04 ` Jiang, YuX
2021-04-29  7:36   ` Jiang, YuX [this message]
2021-04-29 10:38 ` Jiawen Wu
2021-04-29 11:20   ` Ferruh Yigit

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