DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ju-Hyoung Lee <juhlee@microsoft.com>
To: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Luca Boccassi <Luca.Boccassi@microsoft.com>,
	Ju-Hyoung Lee <juhlee@microsoft.com>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 19.05-rc1
Date: Thu, 11 Apr 2019 15:36:42 +0000	[thread overview]
Message-ID: <MW2PR2101MB098613A1BB7AEBCB62D64174DA2F0@MW2PR2101MB0986.namprd21.prod.outlook.com> (raw)
Message-ID: <20190411153642.QzBuu8BQyxY1zS3y_W9tPCmLXnQu3zwUpt36PYFREUE@z> (raw)
In-Reply-To: <MW2PR2101MB0986C47C07FF1B829861BBD1DA2F0@MW2PR2101MB0986.namprd21.prod.outlook.com>

Greeting, here is 19.05-rc1 test result.

VERIFY-SRIOV-FAILSAFE-FOR-DPDK test failed at https://git.dpdk.org/dpdk/snapshot/dpdk-19.05-rc1.tar.xz (tagged for v19.05-rc1, 0507931311e4daf2468f2f7d1295e8a306662aad)

There were a few patches for mlx5 and testpmd following, and VERIFY-SRIOV-FAILSAFE-FOR-DPDK passed at http://git.dpdk.org/next/dpdk-next-net/commit/?id=417eeb5361ec29ce16052306b274d27b42ed33b1 (app/testpmd: fix txonly mode packet headers)

Here is original test summary page based on 19.05-rc1 tag.

[LISAv2 Test Results Summary]
Test Run On           : 04/08/2019 18:32:36
ARM Image Under Test  : Canonical : UbuntuServer : 18.04-LTS : latest
Total Test Cases      : 10 (9 Passed, 1 Failed, 0 Aborted, 0 Skipped)
Total Time (dd:hh:mm) : 0:5:1

   ID TestArea             TestCaseName                                                                TestResult TestDuration(in minutes) 
-------------------------------------------------------------------------------------------------------------------------------------------
    1 DPDK                 VERIFY-DPDK-BUILD-AND-TESTPMD-TEST                                                PASS                23.71 
    2 DPDK                 VERIFY-SRIOV-FAILSAFE-FOR-DPDK                                                    FAIL                59.67 
	DPDK-TESTPMD : Initial SRIOV : DPDK 19.05.0-rc1 : TxPPS : 12647832 : RxPPS : 0 
	DPDK-TESTPMD : Synthetic : DPDK 19.05.0-rc1 : TxPPS : 626848 : RxPPS : 0 
	DPDK-TESTPMD : Re-Enable SRIOV : DPDK 19.05.0-rc1 : TxPps : 12896016 : RxPps : 0 
    3 DPDK                 PERF-DPDK-SINGLE-CORE-PPS-DS4                                                     PASS                16.17 
	DPDK-TEST : PASS 
    4 DPDK                 PERF-DPDK-MULTICORE-PPS-F32                                                       PASS                27.91 
	DPDK-TEST : PASS 
    5 DPDK                 VERIFY-DPDK-OVS                                                                   PASS                18.27 
    6 DPDK                 PERF-DPDK-SINGLE-CORE-PPS-DS15                                                    PASS                15.23 
	DPDK-TEST : PASS 
    7 DPDK                 PERF-DPDK-MULTICORE-PPS-DS15                                                      PASS                23.99 
	DPDK-TEST : PASS 
    8 DPDK                 VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC                                               PASS                22.56 
	DPDK-TEST : True 
    9 DPDK                 PERF-DPDK-FWD-PPS-DS15                                                            PASS                20.24 
	DPDK-TEST : PASS 
   10 DPDK                 VERIFY-DPDK-COMPLIANCE                                                            PASS                 8.01

-----Original Message-----
From: announce <announce-bounces@dpdk.org> On Behalf Of Thomas Monjalon
Sent: Friday, April 5, 2019 3:56 PM
To: announce@dpdk.org
Subject: [dpdk-announce] release candidate 19.05-rc1

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%3Dv19.05-rc1&amp;data=02%7C01%7CJuhlee%40microsoft.com%7Ca46239b912d44015256508d6ba19d5a7%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636901017457447225&amp;sdata=9bHq%2B0zCy77e52C97dVnZQ9rm6Ds%2B6dEU5iBFNs8y8g%3D&amp;reserved=0

After one big and one short cycle releases, this one looks normal, delivering -rc1, almost on time, with 678 patches.

The release notes so far:
	https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdoc.dpdk.org%2Fguides%2Frel_notes%2Frelease_19_05.html&amp;data=02%7C01%7CJuhlee%40microsoft.com%7Ca46239b912d44015256508d6ba19d5a7%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636901017457447225&amp;sdata=gTf0Ck90aoohvXQ36b1q1WHXdyX1icmbq6JTTZmfG08%3D&amp;reserved=0
Please think about updating the release notes when you add a feature.

Highlights of 19.05-rc1, grouped by category:
General:
	- helloworld on Windows
	- C11 memory ordering in spinlock, rwlock and new ticketlock
	- lock-free extendable bucket in hash library
	- stack library and lock-free stack mempool handler
	- DMA mapping for external memory
Networking:
	- min/max MTU info
	- iterators for multi-ports device
	- AF_XDP PMD
	- ice: vector instructions
	- ice: package download
	- i40e:  VXLAN-GPE
	- ixgbe: promiscuous mode on VF
	- ixgbe: loopback for X540/X550
	- mlx5: direct rule
	- mlx4: secondary process
	- failsafe: secondary process
Cryptography:
	- more algorithms in IPsec library
	- qat asymmetric crypto
Applications:
	- live testpmd statistics
	- optimized testpmd macswap mode for Arm
	- optimized testpmd txonly mode
	- multiple flows with testpmd txonly mode

Some features are expected in 19.05-rc2:
	- RCU library
	- timer management in multi-process
	- memif PMD
	- nfb PMD
	- ipn3ke PMD

We have one month to complete this release cycle.
19.05-rc2 is expected on 10th of April.

Thank you everyone


PS: some extra informations below

About the previous release 19.02.0, it has been decided to have no maintenance release 19.02.1 because of a lack of interest.

Only one week remaining to propose a talk for China Summit:
	https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.dpdk.org%2Fevent%2Fdpdk-china-june-24th-2019&amp;data=02%7C01%7CJuhlee%40microsoft.com%7Ca46239b912d44015256508d6ba19d5a7%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636901017457447225&amp;sdata=1hC5m0djfTpHDdCdG%2FAYmA0EVOKAuEK66jw0BtHkfho%3D&amp;reserved=0



  parent reply	other threads:[~2019-04-11 15:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-05 22:55 Thomas Monjalon
2019-04-05 22:55 ` Thomas Monjalon
2019-04-07  9:10 ` Thomas Monjalon
2019-04-07  9:10   ` Thomas Monjalon
     [not found] ` <MW2PR2101MB0986C47C07FF1B829861BBD1DA2F0@MW2PR2101MB0986.namprd21.prod.outlook.com>
2019-04-11 15:36   ` Ju-Hyoung Lee [this message]
2019-04-11 15:36     ` Ju-Hyoung Lee

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=MW2PR2101MB098613A1BB7AEBCB62D64174DA2F0@MW2PR2101MB0986.namprd21.prod.outlook.com \
    --to=juhlee@microsoft.com \
    --cc=Luca.Boccassi@microsoft.com \
    --cc=dev@dpdk.org \
    --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).