From: Yuanhan Liu <yliu@fridaylinux.org>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: dpdk stable <stable@dpdk.org>, dev@dpdk.org
Subject: Re: [dpdk-stable] 16.11.3 (LTS) patches review and test
Date: Mon, 21 Aug 2017 11:40:11 +0800 [thread overview]
Message-ID: <20170821034011.GO9612@yliu-home> (raw)
In-Reply-To: <c9b5eef5-9b7c-2b86-c637-e75a1e386fed@redhat.com>
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 <qi.z.zhang@intel.com>
> 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
--yliu
next prev parent reply other threads:[~2017-08-21 3:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 10:45 Yuanhan Liu
2017-08-18 17:29 ` Kevin Traynor
2017-08-21 3:40 ` Yuanhan Liu [this message]
2017-08-21 8:23 ` Ferruh Yigit
2017-08-21 9:23 ` Yuanhan Liu
2017-08-21 15:25 ` Kevin Traynor
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=20170821034011.GO9612@yliu-home \
--to=yliu@fridaylinux.org \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=stable@dpdk.org \
/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).