DPDK patches and discussions
 help / color / mirror / Atom feed
From: Abhishek Marathe <Abhishek.Marathe@microsoft.com>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Lili Deng <Lili.Deng@microsoft.com>,
	Ju-Hyoung Lee <juhlee@microsoft.com>
Subject: Re: [dpdk-dev] [EXTERNAL] [dpdk-announce] release candidate 20.02-rc4
Date: Wed, 18 Mar 2020 00:54:01 +0000	[thread overview]
Message-ID: <BN6PR21MB0628F80051D2A144926EC6249EF70@BN6PR21MB0628.namprd21.prod.outlook.com> (raw)
In-Reply-To: <2014314.GUh0CODmnK@xps>

Hi,

Replying to this email thread as I'm not able to find original thread for 20.02 review and test.

Our findings while testing v20.02:
1. We did see issues against SLES15 SP1 and RHEL 7 RAW with CX4, after investigation, issues are fixed by installing Mellanox driver.

DPDK_SOURCE_URL=https://git.dpdk.org/dpdk/snapshot/dpdk-v20.02.tar.gz

Test case description:
* VERIFY-DPDK-COMPLIANCE - verifies kernel is supported and that the build is successful
* VERIFY-DPDK-BUILD-AND-TESTPMD-TEST - verifies using testpmd that packets can be sent from a VM to another VM
* VERIFY-SRIOV-FAILSAFE-FOR-DPDK - disables/enables Accelerated Networking for the NICs under test and makes sure DPDK works in both scenarios
* VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC - disables/enables Accelerated Networking for the NICs while generating traffic using testpmd

* PERF-DPDK-FWD-PPS-DS15 - verifies DPDK forwarding performance using testpmd on 2, 4, 8 cores, rx and io mode on size Standard_DS15_v2
* PERF-DPDK-SINGLE-CORE-PPS-DS4 - verifies DPDK performance using testpmd on 1 core, rx and io mode on size Standard_DS4_v2
* PERF-DPDK-SINGLE-CORE-PPS-DS15 - verifies DPDK performance using testpmd on 1 core, rx and io mode on size Standard_DS15_v2
* PERF-DPDK-MULTICORE-PPS-DS15 - verifies DPDK performance using testpmd on 2, 4, 8 cores, rx and io mode on size Standard_DS15_v2
* PERF-DPDK-MULTICORE-PPS-F32 - verifies DPDK performance using testpmd on 2, 4, 8, 16 cores, rx and io mode on size Standard_F32s_v2

* DPDK-RING-LATENCY - verifies DPDK CPU latency using https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fshemminger%2Fdpdk-ring-ping.git&amp;data=02%7C01%7CAbhishek.Marathe%40microsoft.com%7Caa457975b80d4b905a4708d748949f33%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637057675470614018&amp;sdata=grffUwKPmgVqikIpQzx6%2Bd9D2rpuCDnqvH%2FVIe5iUa4%3D&amp;reserved=0
* VERIFY-DPDK-PRIMARY-SECONDARY-PROCESSES - verifies primary / secondary processes support for DPDK. Runs only on RHEL and Ubuntu distros with Linux kernel >= 4.20

* VERIFY-DPDK-OVS - builds OVS with DPDK support and tests if the OVS DPDK ports can be created. Runs only on Ubuntu distro.
* VERIFY-DPDK-VPP - builds VPP with DPDK support and tests if the VPP ports are present. Runs only on RHEL and Ubuntu distros.
* VERIFY-DPDK-NFF-GO - builds NFF-GO with DPDK support and runs the functional tests from the NFF-GO repository. Runs only on Ubuntu distro. 

Azure images:
Canonical UbuntuServer 16.04-LTS latest
Canonical UbuntuServer 18.04-DAILY-LTS latest
RedHat RHEL 7-RAW latest 
RedHat RHEL 7.5 latest 
Openlogic CentOS 7.5 latest
SUSE SLES-15-sp1 gen1 latest
 
Test case status:
VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC PASS
VERIFY-DPDK-BUILD-AND-TESTPMD-TEST PASS
VERIFY-SRIOV-FAILSAFE-FOR-DPDK PASS
VERIFY-DPDK-COMPLIANCE PASS
VERIFY-DPDK-OVS PASS
VERIFY-DPDK-RING-LATENCY PASS
PERF-DPDK-FWD-PPS-DS15 PASS
PERF-DPDK-SINGLE-CORE-PPS-DS4 PASS
PERF-DPDK-SINGLE-CORE-PPS-DS15 PASS
PERF-DPDK-MULTICORE-PPS-DS15 PASS
PERF-DPDK-MULTICORE-PPS-F32 PASS

Regards,
Abhishek

-----Original Message-----
From: announce <announce-bounces@dpdk.org> On Behalf Of Thomas Monjalon
Sent: Saturday, February 22, 2020 1:08 PM
To: announce@dpdk.org
Subject: [EXTERNAL] [dpdk-announce] release candidate 20.02-rc4

A new DPDK release candidate is ready for testing:
	https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.dpdk.org%2Fdpdk%2Ftag%2F%3Fid%3Dv20.02-rc4&amp;data=02%7C01%7CAbhishek.Marathe%40microsoft.com%7C7386440a2e714d37831408d7b7db55ca%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637180024975203059&amp;sdata=XF8S3GF8oUsBXh7O2NIgz002HM611Ob6bBHfPbThZZ0%3D&amp;reserved=0
76 patches were integrated.
This is small enough to be confident about closing 20.02 soon.

The release notes so far:
	https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdoc.dpdk.org%2Fguides%2Frel_notes%2Frelease_20_02.html&amp;data=02%7C01%7CAbhishek.Marathe%40microsoft.com%7C7386440a2e714d37831408d7b7db55ca%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637180024975203059&amp;sdata=LMP4KBmgrDdPCeE%2B6IW8ZJDHOJYCJl%2Fr6WnA647xVnY%3D&amp;reserved=0
Please add your tested platforms to the list:
	https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdoc.dpdk.org%2Fguides%2Frel_notes%2Frelease_20_02.html%23tested-platforms&amp;data=02%7C01%7CAbhishek.Marathe%40microsoft.com%7C7386440a2e714d37831408d7b7db55ca%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637180024975203059&amp;sdata=Z9u9LjrUUe%2FqHk2o34eYz2erZuhmQCqr16YUIyXvXnk%3D&amp;reserved=0
Some deprecation notices are pending for review.

This is the last release candidate for DPDK 20.02.
Please share some release validation results by replying to this message (at dev@dpdk.org).
If no critical issue is reported, 20.02 will be closed on Tuesday 25th.

If you are preparing the next release cycle, please send your v1 patches before the 20.05 proposal deadline, which will happen on March 18th.
It is also time to build an estimated roadmap for the next cycles.

Thank you everyone



      parent reply	other threads:[~2020-03-19  8:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-22 21:08 [dpdk-dev] " Thomas Monjalon
2020-02-25  9:58 ` Ali Alnubani
2020-02-25 14:37   ` Xu, Qian Q
2020-02-25 14:44     ` Thomas Monjalon
2020-02-25 15:27       ` Raslan Darawsheh
2020-03-18  0:54 ` Abhishek Marathe [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=BN6PR21MB0628F80051D2A144926EC6249EF70@BN6PR21MB0628.namprd21.prod.outlook.com \
    --to=abhishek.marathe@microsoft.com \
    --cc=Lili.Deng@microsoft.com \
    --cc=dev@dpdk.org \
    --cc=juhlee@microsoft.com \
    --cc=ktraynor@redhat.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).