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.02-rc3
Date: Tue, 9 Feb 2021 08:11:55 +0000	[thread overview]
Message-ID: <8a317b8958854b6fbdf1af323345cf12@intel.com> (raw)
In-Reply-To: <5305610.D7H1GXTtC2@thomas>

All,

Update the test status for Intel part. Validation test are almost finished. 
 
# 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 8.3, CentOS Stream 8, etc.
			- All passed.
		*Compile: cover the CFLAGES(O0/O1/O2/O3) with popular OS such as Ubuntu20.04 and CentOS 8.3. 
			- All passed.

	*PF(i40e, ixgbe and igb): test scenarios including RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc. 
		- All test are done. Only 1 bug is found. 4 issues found in RC2 are fixed in RC3. 
                             
	*VF(i40e, ixgbe and igb): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc.
		- All passed except known issue. No new issues are 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 test are done. No new issues are found. 4 issues about QinQ found on RC2 are 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.
		- All passed. The performance is consistent with RC2. 
 
	* Power and IPsec: 
		* Power: test scenarios including bi-direction/Telemetry/Empty Poll Lib/Priority Base Frequency and so on. 
 			- Not test yet.                             
 		* IPsec: No test due to there's no codes changes.    
 
 # 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.0u1, etc.
		- All passed except known issue. 4 Virtio related issue are fixed in RC3.
                  
	* Cryptodev: 
		*Function test: test scenarios including Cryptodev API testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
			- All passed.
		*Performance test: test scenarios including Thoughput Performance /Cryptodev Latency, etc.
			- The performance is consistent with RC2.

Best regards,
Jiang, Yu

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Thomas Monjalon
> Sent: Saturday, February 6, 2021 4:29 AM
> To: announce@dpdk.org
> Subject: [dpdk-dev] [dpdk-announce] release candidate 21.02-rc3
> 
> A new DPDK release candidate is ready for testing:
> 	https://git.dpdk.org/dpdk/tag/?id=v21.02-rc3
> 
> There are 80 new patches in this snapshot.
> 
> Release notes:
> 	https://doc.dpdk.org/guides/rel_notes/release_21_02.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.
> 
> The -rc4 should include only critical bug fixes, doc and tooling.
> 
> Please think about sharing your roadmap for DPDK 21.05.
> 
> Thank you everyone
> 


      reply	other threads:[~2021-02-09  8:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05 20:28 Thomas Monjalon
2021-02-09  8:11 ` Jiang, YuX [this message]

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=8a317b8958854b6fbdf1af323345cf12@intel.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).