From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Liang Zhang <zhangliang@bigo.sg>, dev@dpdk.org
Cc: 3chas3@gmail.com, ktraynor@redhat.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] net/bonding: fix lacp negotiation failed
Date: Thu, 21 Mar 2019 10:24:23 +0000 [thread overview]
Message-ID: <06501a46-548e-a88d-6389-9de4f9008814@intel.com> (raw)
Message-ID: <20190321102423.nsB-rF-oUmJrbXd_i_75zZOj1GPR5PSHPL8Lt8o_7kE@z> (raw)
In-Reply-To: <1553160576-27363-1-git-send-email-zhangliang@bigo.sg>
On 3/21/2019 9:29 AM, Liang Zhang wrote:
> When monitor(port-mirroring) traffic from other lacp port-channel,
> rx_machine_update may recieving other lacp negotiation packets.
> Thus bond mode 4 will negotiation failed.
>
> Fixes: 112891cd27e5 ("net/bonding: add dedicated HW queues for LACP control")
> Cc: stable@dpdk.org
>
> Signed-off-by: Liang Zhang <zhangliang@bigo.sg>
Carrying the ack from previous version:
Acked-by: Chas Williams <chas3@att.com>
next prev parent reply other threads:[~2019-03-21 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 9:29 [dpdk-dev] " Liang Zhang
2019-03-21 9:29 ` Liang Zhang
2019-03-21 10:24 ` Ferruh Yigit [this message]
2019-03-21 10:24 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
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=06501a46-548e-a88d-6389-9de4f9008814@intel.com \
--to=ferruh.yigit@intel.com \
--cc=3chas3@gmail.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=stable@dpdk.org \
--cc=zhangliang@bigo.sg \
/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).