From: Sachin Saxena <sachin.saxena@nxp.com>
To: "dev@dpdk.org" <dev@dpdk.org>, Rajan Gupta <rajan.gupta@nxp.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 19.11-rc4
Date: Thu, 28 Nov 2019 10:29:49 +0000 [thread overview]
Message-ID: <VI1PR04MB484591121B89786B9AA7BC24E3470@VI1PR04MB4845.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <257c086cee51c1ddba6dbf907d8cabd2a2500b0e.camel@microsoft.com>
Hi,
We are fine with test report on release candidate 19.11-rc4.
Following Test Cases have been validated successfully on NXP platforms:
dpdk_l2fwd_function
dpdk_l3fwd_function
dpdk_l2fwd-crypto_caam_function
dpdk_ovs-host_function
dpdk_multiprocess_symmetric_mp
dpdk_multiprocess_simple_mp
dpdk_multiprocess_symmetric_mp_qdma
dpdk_multiprocess_l2fwd-crypto
dpdk_testpmd_fwd_jumbo
dpdk_timer_function
dpdk_ip_fragmentation
dpdk_l3fwd_acl
dpdk_l2fwd_keepalive
dpdk_test_function
dpdk_test_crypto_perf
dpdk_skelton_function
dpdk_cmdline_function
dpdk_rxtx_callback_function
dpdk_ethtool_function
dpdk_ipv4_multicast
regards,
Sachin Saxena
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Luca Boccassi
> Sent: Thursday, November 28, 2019 3:21 PM
> To: dev@dpdk.org
> Cc: thomas@monjalon.net; Ju-Hyoung Lee <juhlee@microsoft.com>;
> Abhishek Marathe <Abhishek.Marathe@microsoft.com>
> Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 19.11-rc4
>
> Hi,
>
> Here's the report from the automated Jenkins pipeline at MSFT - QA team
> will be out for Thanksgiving this week, they can chip in next week for more
> details, but I do not see any blocking issue being highlighted - just the usual
> small performance issue that is already being investigated separately.
>
>
> DPDK v19.11-rc4 was validated on Azure for 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 latest.
> Tested with Mellanox and netvsc poll-mode drivers.
> The tests were executed using LISAv2 framework (
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithu
> b.com%2FLIS%2FLISAv2&data=02%7C01%7Csachin.saxena%40nxp.com
> %7C64f8b403f28b4cab85c108d773e8834d%7C686ea1d3bc2b4c6fa92cd99c
> 5c301635%7C0%7C0%7C637105314779183163&sdata=Z7XQKAnhtgW
> wqASYhMtwMFRfuDPZL8fdJSGUfqfZqgM%3D&reserved=0 ).
>
> 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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithu
> b.com%2Fshemminger%2Fdpdk-ring-
> ping&data=02%7C01%7Csachin.saxena%40nxp.com%7C64f8b403f28b4
> cab85c108d773e8834d%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C
> 0%7C637105314779183163&sdata=u6QPFQ%2Bygf9M%2BL7i39LSIpc
> 8T37j8jQRywobmWuQhkc%3D&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.
>
> DPDK job exited with status: UNSTABLE.
>
> Test results for DPDK 'v19.11-rc4' and Azure image: 'Canonical UbuntuServer
> 16.04-LTS latest':
>
> * PERF-DPDK-SINGLE-CORE-PPS-DS4: FAILED
> * VERIFY-DPDK-OVS: PASSED
> * VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED
> * VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
> * PERF-DPDK-MULTICORE-PPS-F32: PASSED
> * VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED
>
> Test results for DPDK 'v19.11-rc4' and Azure image: 'Canonical UbuntuServer
> 18.04-DAILY-LTS latest':
>
> * PERF-DPDK-SINGLE-CORE-PPS-DS4: PASSED
> * VERIFY-DPDK-OVS: PASSED
> * VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED
> * VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
> * PERF-DPDK-MULTICORE-PPS-F32: FAILED
> * VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED
>
> Test results for DPDK 'v19.11-rc4' and Azure image: 'RedHat RHEL 7-RAW
> latest':
>
> * PERF-DPDK-SINGLE-CORE-PPS-DS4: PASSED
> * VERIFY-DPDK-OVS: SKIPPED
> * VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED
> * VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
> * PERF-DPDK-MULTICORE-PPS-F32: FAILED
> * VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED
>
> Test results for DPDK 'v19.11-rc4' and Azure image: 'RedHat RHEL 7.5 latest':
>
> * PERF-DPDK-SINGLE-CORE-PPS-DS4: PASSED
> * VERIFY-DPDK-OVS: SKIPPED
> * VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED
> * VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
> * PERF-DPDK-MULTICORE-PPS-F32: PASSED
> * VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED
>
> Test results for DPDK 'v19.11-rc4' and Azure image: 'Openlogic CentOS 7.5
> latest':
>
> * PERF-DPDK-SINGLE-CORE-PPS-DS4: PASSED
> * VERIFY-DPDK-OVS: SKIPPED
> * VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED
> * VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
> * PERF-DPDK-MULTICORE-PPS-F32: FAILED
> * VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED
>
> Test results for DPDK 'v19.11-rc4' and Azure image: 'SUSE SLES 15 latest':
>
> * PERF-DPDK-SINGLE-CORE-PPS-DS4: FAILED
> * VERIFY-DPDK-OVS: SKIPPED
> * VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED
> * VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
> * PERF-DPDK-MULTICORE-PPS-F32: PASSED
> * VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED
>
> On Wed, 2019-11-27 at 00:56 +0100, Thomas Monjalon wrote:
> > A new DPDK release candidate is ready for testing:
> >
> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.
> > dpdk.org%2Fdpdk%2Ftag%2F%3Fid%3Dv19.11-
> rc4&data=02%7C01%7Csachin.s
> >
> axena%40nxp.com%7C64f8b403f28b4cab85c108d773e8834d%7C686ea1d3
> bc2b4c6fa
> >
> 92cd99c5c301635%7C0%7C0%7C637105314779193156&sdata=9Ohpf
> XEmVuNtXej
> > 7xJRW2J7e98hNw5JFe6yurKSUExQ%3D&reserved=0
> >
> > 93 patches were integrated.
> >
> > The release notes so far:
> >
> >
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdoc.d
> >
> pdk.org%2Fguides%2Frel_notes%2Frelease_19_11.html&data=02%7C0
> 1%7Cs
> >
> achin.saxena%40nxp.com%7C64f8b403f28b4cab85c108d773e8834d%7C686
> ea1d3bc
> >
> 2b4c6fa92cd99c5c301635%7C0%7C0%7C637105314779193156&sdat
> a=yTs7hRHL
> > raBaWIMP%2B3lEzAcofiNVWY4N2l7PhEPEvFs%3D&reserved=0
> >
> > It should be completed with a list of tested hardware.
> >
> > This is the last release candidate for DPDK 19.11.
> > After -rc4 only critical bug fixes and doc updates should be accepted.
> >
> > The major release should be done in a couple of days (Thanksgiving?).
> > Please share some release validation results by replying to this
> > message (at dev@dpdk.org ).
> >
> > If you are preparing the next release cycle, please send your v1
> > patches before the 20.02 proposal deadline, which will happen on
> > December 6th.
> > It is also time to build an estimated roadmap for the next cycles.
> >
> > Thank you everyone
> >
> >
> >
> --
> Kind regards,
> Luca Boccassi
next prev parent reply other threads:[~2019-11-28 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 23:56 Thomas Monjalon
2019-11-27 18:16 ` Stokes, Ian
2019-11-28 9:51 ` Luca Boccassi
2019-11-28 10:29 ` Sachin Saxena [this message]
2019-11-28 13:14 ` Xu, Qian Q
2019-11-28 12:25 ` Ali Alnubani
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=VI1PR04MB484591121B89786B9AA7BC24E3470@VI1PR04MB4845.eurprd04.prod.outlook.com \
--to=sachin.saxena@nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=rajan.gupta@nxp.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).