From: Kevin Traynor <ktraynor@redhat.com>
To: Liang Zhang <zhangliang@bigo.sg>, dev@dpdk.org
Cc: 3chas3@gmail.com
Subject: Re: [dpdk-dev] [PATCH] bonding: fix lacp negotiation failed
Date: Tue, 19 Mar 2019 16:03:17 +0000 [thread overview]
Message-ID: <6d84e190-5fef-2b65-2b02-377d22de0409@redhat.com> (raw)
In-Reply-To: <1552640761-16834-1-git-send-email-zhangliang@bigo.sg>
On 15/03/2019 09:06, 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.
>
Please add a 'Fixes:' tag, and if appropriate for backport to stable
branches, also a 'Cc: stable@dpdk.org' tag.
> Signed-off-by: Liang Zhang <zhangliang@bigo.sg>
> ---
next prev parent reply other threads:[~2019-03-19 16:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 9:06 Liang Zhang
2019-03-15 9:06 ` Liang Zhang
2019-03-18 13:45 ` Chas Williams
2019-03-18 13:45 ` Chas Williams
2019-03-19 16:03 ` Kevin Traynor [this message]
2019-03-19 16:03 ` Kevin Traynor
-- strict thread matches above, loose matches on Subject: below --
2019-03-13 13:23 Liang Zhang
2019-03-13 18:02 ` Chas Williams
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=6d84e190-5fef-2b65-2b02-377d22de0409@redhat.com \
--to=ktraynor@redhat.com \
--cc=3chas3@gmail.com \
--cc=dev@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).