From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 550] Only one bond link is usable with 802.3ad LACP (mode 4)
Date: Fri, 09 Oct 2020 18:34:05 +0000 [thread overview]
Message-ID: <bug-550-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=550
Bug ID: 550
Summary: Only one bond link is usable with 802.3ad LACP (mode
4)
Product: DPDK
Version: 20.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: kiran.kn80@gmail.com
Target Milestone: ---
This commit is causing only one bond slave link to forward traffic -
https://github.com/DPDK/dpdk/commit/56cbc08173995d6d57bd5927dfe9b11ad269bf8d
Testing with Juniper QFX switch.
Only one link satisfies this condition -
if (is_same_ether_addr(&partner->port_params.system,
&internals->mode4.mac_addr)) {
/* This LACP frame is sending to the bonding port
* so pass it to rx_machine.
*/
rx_machine(internals, slave_id, &lacp->lacpdu);
}
For other links, the system id is different than the bond MAC and so
rx_machine() never gets called.
Discussed this with Doherty, Declan <declan.doherty@intel.com>
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-10-09 18:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-550-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.