* [dpdk-dev] [Bug 550] Only one bond link is usable with 802.3ad LACP (mode 4)
@ 2020-10-09 18:34 bugzilla
0 siblings, 0 replies; only message in thread
From: bugzilla @ 2020-10-09 18:34 UTC (permalink / raw)
To: dev
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-10-09 18:34 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-09 18:34 [dpdk-dev] [Bug 550] Only one bond link is usable with 802.3ad LACP (mode 4) bugzilla
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).