From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [dpdk-stable] 16.11.3 (LTS) patches review and test Date: Mon, 21 Aug 2017 09:23:24 +0100 Message-ID: <2d8dbb48-978f-94fb-1282-8b5c4ea30220@intel.com> References: <20170818104545.GN9612@yliu-home> <20170821034011.GO9612@yliu-home> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: dpdk stable , dev@dpdk.org To: Yuanhan Liu , Kevin Traynor Return-path: In-Reply-To: <20170821034011.GO9612@yliu-home> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 8/21/2017 4:40 AM, Yuanhan Liu wrote: > On Fri, Aug 18, 2017 at 06:29:02PM +0100, Kevin Traynor wrote: >> On 08/18/2017 11:45 AM, Yuanhan Liu wrote: >>> Hi all, >>> >>> Here is a list of patches targeted for LTS release 16.11.3. Please >>> help review and test. The planned date for the final release is 30th, >>> Aug. Before that, please let me know if anyone has objections with >>> these patches being applied. >>> >>> These patches are located at branch 16.11 of dpdk-stable repo: >>> http://dpdk.org/browse/dpdk-stable/ >>> >>> Thanks. >>> >>> --yliu >>> >> >> Hi Yuanhan, >> >> I think this one should go in too, as OVS hits this and writes back the >> wrong watermark value to the shared register which can cause problems >> for other ports. I've applied and tested it with DPDK 16.11. >> >> commit 0e61ab56e01655f02bfe4e6249e032e864b0f5dd >> Author: Qi Zhang >> Date: Thu Aug 10 18:48:07 2017 +0800 >> >> net/i40e: fix flow control watermark mismatch >> >> Flow control watermark is not read out correctly, >> that may cause an application who not intend to change >> watermark but does change it with a rte_eth_dev_flow_ctrl_set >> call right after rte_eth_dev_flow_ctrl_get. > > Weird, I couldn't find this commit: > > $ git show 0e61ab56e01655f02bfe4e6249e032e864b0f5dd > fatal: bad object 0e61ab56e01655f02bfe4e6249e032e864b0f5dd The commit is in next-net. Not sure how to proceed, any idea? > > --yliu >