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-rc2
Date: Mon, 1 Feb 2021 09:49:54 +0000	[thread overview]
Message-ID: <c2bd98a6da8d4955b19b8838c9bf60b7@intel.com> (raw)
In-Reply-To: <2701263.OCiMXv1sLx@thomas>

All,
Update the test status for Intel part. Till now 50% is executed and no critical issue blocked the test.

# Basic Intel(R) NIC testing
  * PF/VF(i40e,ixgbe and igb): 90% is tested. 2 issues are found but not are big issue.
  * PF/VF(ICE): 40% is tested. 2 issues are found regarding vf_vlan_strip and mac_vlan_pppoe but not are big issue.
  * Build or compile: 
	- Build: 100%. No issue is found.
	- Compile: Not start yet. Working on it.
  * Intel NIC single core/NIC performance:  60% is tested. No big performance drop issue.
  * Power and IPsec: Not start yet.
  * Other 21.02 new features: 30% is tested. 2 issues are found till now but not critical issue.
   
 # Basic cryptodev and virtio testing
   * Virtio: 100% is tested. Total find 3 bugs but not critical issues.
	- 2 Bugzilla bugs(https://bugs.dpdk.org/show_bug.cgi?id=630  & https://bugs.dpdk.org/show_bug.cgi?id=631)
	- 1 Bug is failed to start dpdk-dump.
   * Cryptodev: 
	- Function test: 100% is tested. No new issue is found. 
	- Performance is testing.

Best regards,
Jiang, Yu

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Thomas Monjalon
> Sent: Saturday, January 30, 2021 9:23 AM
> To: announce@dpdk.org
> Subject: [dpdk-dev] [dpdk-announce] release candidate 21.02-rc2
> 
> A new DPDK release candidate is ready for testing:
> 	https://git.dpdk.org/dpdk/tag/?id=v21.02-rc2
> 
> There are 293 new patches in this snapshot, more than expected for a light
> release cycle.
> 
> Release notes:
> 	https://doc.dpdk.org/guides/rel_notes/release_21_02.html
> 
> Highlights of 21.02-rc2:
> 	- new pmdinfogen with Windows support
> 	- power management for core polling single ethdev queue
> 	- Marvell OCTEON TX EP net PMD
> 	- Mellanox compress PMD
> 	- Virtio PMD rework
> 
> Please test and report issues on bugs.dpdk.org.
> 
> The -rc3 should include only some bug fixes, cleanups, doc and tooling.
> 
> Next Thursday (February 4) should be the day of closing 21.02-rc3.
> The goal is to complete the release before the Chinese New Year to allow a
> quiet rest during the Spring Festival.
> 
> Thank you everyone
> 


  reply	other threads:[~2021-02-01  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-30  1:23 Thomas Monjalon
2021-02-01  9:49 ` Jiang, YuX [this message]
2021-02-04  5:12   ` Jiang, YuX
2021-02-04 22:07 ` Thinh Tran
2021-02-07 12:59 ` 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=c2bd98a6da8d4955b19b8838c9bf60b7@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).