From: "Chen, WeichunX" <weichunx.chen@intel.com>
To: "Kavanagh, Mark B" <mark.b.kavanagh@intel.com>,
Yuanhan Liu <yliu@fridaylinux.org>, dpdk stable <stable@dpdk.org>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
"Wei, FangfangX" <fangfangx.wei@intel.com>,
"Yao, Lei A" <lei.a.yao@intel.com>,
"Wang, FeiX Y" <feix.y.wang@intel.com>,
"Pei, Yulong" <yulong.pei@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] 17.05.1 patches review and test
Date: Thu, 29 Jun 2017 01:31:31 +0000 [thread overview]
Message-ID: <2F49FDB6EFE3E047BF58B7A7DC05541F5350E72B@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <DC5AD7FA266D86499789B1BCAEC715F8B1C66787@IRSMSX101.ger.corp.intel.com>
Hi Yuanhan and all
We have done all of the test jobs on stable release 17.05.1. All pass and no new issues.
More detailed information attached.
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Kavanagh, Mark B
Sent: Wednesday, June 28, 2017 8:49 PM
To: Yuanhan Liu <yliu@fridaylinux.org>; dpdk stable <stable@dpdk.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] 17.05.1 patches review and test
>From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Yuanhan Liu
>Sent: Thursday, June 22, 2017 2:08 PM
>To: dpdk stable <stable@dpdk.org>
>Cc: dev@dpdk.org
>Subject: [dpdk-dev] 17.05.1 patches review and test
>
>Hi all,
>
>I'm doing an unexpected stable release, which is expected to be
>released in about two months. The reason I'm doing it is there is an
>import bug fix commit that is needed for OVS 2.8 release. The fix is a
>vhost-user commit comes from me. Well, unfortunately, I'm also the
>author of the original bug :/
>
>So I'm doing an urgent release. That also means we will have another
>17.05 release (17.05.2) shortly after v17.08 is out.
>
>And here is a list of patches targeted for this release. Please help
>review and test. The planned date for the final release is 30, June.
>Before that, please shout if anyone has objections.
>
>These patches are located at branch 17.05 of dpdk-stable repo:
> http://dpdk.org/browse/dpdk-stable/
>
Hi Yuanhan,
Thanks for making this release available ahead of schedule - it puts OvS in a good position to upgrade the supported version of DPDK in OvS v2.8.0 (due ~mid-August).
I can confirm that the OvS team has performed selective validation on the following DPDK-dependent OvS features:
- Jumbo frames
- vhost NUMA (broken in 17.05 release)
- Rate Limiting
- QoS
- VxLAN tunneling
- Rx checksum offload
- Flow control
- Addition/deletion of vdevs
As such, we're happy to proceed with the 17.05.1 release.
Thanks once again,
Mark
>Thanks.
>
> --yliu
>
>---
>Ajit Khaparde (1):
> net/bnxt: fix reporting of link status
>
>Alejandro Lucero (1):
> vfio: fix array bounds check
>
>Andrew Rybchenko (1):
> net/sfc: add Tx queue flush failed flag for sanity
>
>Andy Moreton (2):
> net/sfc/base: fix error code usage in common code
> net/sfc/base: let caller know that queue is already flushed
>
>Beilei Xing (1):
> app/testpmd: fix creating E-Tag and NVGRE flow rules
>
>Chas Williams (3):
> net/af_packet: handle possible null pointer
> net/af_packet: fix packet bytes counting
> net/ring: fix adding MAC addresses
>
>Dariusz Stojaczyk (2):
> vhost: fix malloc size too small
> vhost: fix guest pages memory leak
>
>David Marchand (1):
> drivers/net: fix vfio kmod dependency
>
>Ferruh Yigit (3):
> kni: fix build with gcc 7.1
> net/enic: fix build with gcc 7.1
> net/mlx5: fix build with gcc 7.1
>
>Harish Patil (1):
> net/qede: fix VXLAN tunnel Tx offload flag setting
>
>Jerin Jacob (1):
> examples/vhost: fix uninitialized descriptor indexes
>
>John Miller (4):
> net/ark: fix buffer not null terminated
> net/ark: fix return code not checked
> net/ark: fix null pointer dereference
> net/ark: fix return value of null not checked
>
>Lee Roberts (1):
> kni: fix build on RHEL 7.4
>
>Markus Theil (1):
> net/igb: fix add/delete of flex filters
>
>Nélio Laranjeiro (1):
> net/mlx5: fix flow application order on stop/start
>
>Pascal Mazon (1):
> net/tap: fix some flow collision
>
>Qi Zhang (3):
> net/ixgbe: fix fdir mask not be reset
> net/i40e: exclude internal packet's byte count
> net/i40e: fix VF statistics
>
>Rahul Lakkireddy (2):
> net/cxgbe: fix port statistics
> net/cxgbe: fix rxq default params for ports under same PF
>
>Shahaf Shuler (1):
> net/mlx5: fix completion buffer size
>
>Shijith Thotton (1):
> net/liquidio: fix MTU calculation from port configuration
>
>Tiwei Bie (1):
> net/virtio: zero the whole memory zone
>
>Wei Dai (1):
> lpm: fix index of tbl8
>
>Wei Zhao (1):
> net/igb: fix checksum valid flags
>
>Wenzhuo Lu (1):
> net/i40e/base: fix Tx error stats on VF
>
>Yongseok Koh (2):
> net/mlx5: fix exception handling
> net/mlx5: fix redundant free of Tx buffer
>
>Yuanhan Liu (1):
> vhost: fix crash on NUMA
prev parent reply other threads:[~2017-06-29 1:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 13:08 [dpdk-stable] " Yuanhan Liu
2017-06-28 12:49 ` [dpdk-stable] [dpdk-dev] " Kavanagh, Mark B
2017-06-29 1:31 ` Chen, WeichunX [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=2F49FDB6EFE3E047BF58B7A7DC05541F5350E72B@SHSMSX101.ccr.corp.intel.com \
--to=weichunx.chen@intel.com \
--cc=dev@dpdk.org \
--cc=fangfangx.wei@intel.com \
--cc=feix.y.wang@intel.com \
--cc=john.mcnamara@intel.com \
--cc=lei.a.yao@intel.com \
--cc=mark.b.kavanagh@intel.com \
--cc=qian.q.xu@intel.com \
--cc=stable@dpdk.org \
--cc=yliu@fridaylinux.org \
--cc=yulong.pei@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).