DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Jiang, YuX" <yux.jiang@intel.com>
To: "Yu, PingX" <pingx.yu@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 21.02-rc1
Date: Wed, 27 Jan 2021 06:27:24 +0000
Message-ID: <ddcde5a760f94e7eb708d508e50e2ac4@intel.com> (raw)
In-Reply-To: <BY5PR11MB39731A80F09848C804F81FA585A00@BY5PR11MB3973.namprd11.prod.outlook.com>

All,
21.02 validation test from Intel part is almost finished and no critical issue is found. 
# Basic Intel(R) NIC testing
  * PF/VF(i40e,ixgbe and igb): 100%. 6 issues are found but no big issues.
  * PF/VF(ICE): 100%. 11 issues are found regarding to AVL rule, rss rule, dcf, ice package and so on. Intel are working on these bugs and expect that we can fix them before RC3.
  * Build or compile: 100%. No issue is found.
  * Intel NIC single core/NIC performance:  100%. No big performance drop issue.
  * Power, IPsec and other SNN/US part: 
        -  IPsec: 100%, no issue is found;
        -  Power: 80% tested, no issue is found till now. Should no big risk.
  *Other 21.02 new features: 100%. No new issue till now.
   
# Basic cryptodev and virtio testing
  * Virtio: 100%. No new issue is found.
  * Cryptodev: 
       - Function:  80%. Cryptodev QAT Ncpm_Symmetric &Multi-process-test is not tested-by. Working on it.
       - Performance: 100%. No data drop.  

Best Regards,
Jiang, Yu

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Yu, PingX
> Sent: Friday, January 22, 2021 6:37 PM
> To: Thomas Monjalon <thomas@monjalon.net>; dev@dpdk.org
> Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 21.02-rc1
> 
> All,
> Update the test status for Intel part. Till now 60% is executed and no critical
> issue blocked the test.
> # Basic Intel(R) NIC testing
>   * PF/VF(i40e,ixgbe and igb): 60% is tested. 3 issues are found but not are big
> issue.
>   * PF/VF(ICE): 50% is tested. 7 issues are found regarding DCF switch_filter,
> RSS rule, rx_vlan created failed and so on.
>   * Build or compile: 100%. No issue is found.
>   * 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. No new issue till now.
> 
>  # Basic cryptodev and virtio testing
>    * Virtio: Done. No new issues except known issue.
>    * Cryptodev: function test is 100%. No new issue is found. Performance is
> testing.
> 
> Regards,
> Yu, Ping
> 
> > -----Original Message-----
> > From: announce <announce-bounces@dpdk.org> On Behalf Of Thomas
> > Monjalon
> > Sent: Wednesday, January 20, 2021 10:07 AM
> > To: announce@dpdk.org
> > Subject: [dpdk-announce] release candidate 21.02-rc1
> >
> > A new DPDK release candidate is ready for testing:
> > 	https://git.dpdk.org/dpdk/tag/?id=v21.02-rc1
> >
> > There are 544 new patches in this snapshot, which is reasonnable for
> > starting a new year.
> >
> > Release notes:
> > 	https://doc.dpdk.org/guides/rel_notes/release_21_02.html
> >
> > Highlights of 21.02-rc1, grouped by category:
> > * Networking
> > 	- power management API
> > 	- generic modify action in flow API
> > 	- GENEVE TLV option in flow API
> > 	- Windows support of i40e and mlx5
> > * Cryptography
> > 	- callback API for enqueue/dequeue
> >
> > Please test and report issues on bugs.dpdk.org.
> >
> > DPDK 21.02-rc2 is expected at the end of this month and may include:
> > 	- Arm build rework
> > 	- pmdinfogen rework
> > 	- power management updates
> > 	- drivers updates
> >
> > Let's be reactive and focus to allow a quiet Chinese New Year.
> > Thank you everyone
> >


  reply	other threads:[~2021-01-27  6:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20  2:06 Thomas Monjalon
2021-01-22 10:36 ` Yu, PingX
2021-01-27  6:27   ` Jiang, YuX [this message]
2021-01-29 20:36 ` Thinh Tran

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=ddcde5a760f94e7eb708d508e50e2ac4@intel.com \
    --to=yux.jiang@intel.com \
    --cc=dev@dpdk.org \
    --cc=pingx.yu@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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git