DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Yu, PingX" <pingx.yu@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "O'Hare, Cathal" <cathal.ohare@intel.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"Zhang, Helin" <helin.zhang@intel.com>,
	"Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: [dpdk-dev] [20.11 RC1]test status update for Intel side(10/23)
Date: Fri, 23 Oct 2020 10:09:57 +0000	[thread overview]
Message-ID: <BY5PR11MB3973A02277503237D4451284851A0@BY5PR11MB3973.namprd11.prod.outlook.com> (raw)

All,
Update the test status for Intel part.  Till now 60% is executed, except performance drop on CVL 100G, no critical issue is found.

# Basic Intel(R) NIC testing

  *   PF/VF(i40e,ixgbe and igb): 60% is tested. 5 meson build issue are found. Some are actually bugs and some need to change the test command based on latest DPDK code.
  *   PF/VF(ICE): 50% is tested. 6 issues are found regarding AVL rule, rss rule, dcf and so on.
  *   Build or compile: 100%. No issue is found.
  *   Intel NIC single core/NIC performance:  60% is tested. Performance drop on CVL 100G is kind of critical issue.
  *   Power and IPsec: Not start yet.
  *   Other 20.11 new features: 40% is tested. No critical issue till now.

# Basic cryptodev and virtio testing

  *   Virtio: 70% is tested. Except known issue, 2 issue about CDBMA are confirming. Maybe DPDK bug.
  *   Cryptodev: function test is 100%. No new issue is found. Performance is testing.

Regards,
Yu Ping


                 reply	other threads:[~2020-10-23 10:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=BY5PR11MB3973A02277503237D4451284851A0@BY5PR11MB3973.namprd11.prod.outlook.com \
    --to=pingx.yu@intel.com \
    --cc=cathal.ohare@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=helin.zhang@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=zhaoyan.chen@intel.com \
    /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).