[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZZtwKFu4GQLQ5AXM@Laptop-X1>
Date: Mon, 8 Jan 2024 11:46:48 +0800
From: Hangbin Liu <liuhangbin@...il.com>
To: Jay Vosburgh <jay.vosburgh@...onical.com>
Cc: Aahil Awatramani <aahila@...gle.com>,
David Dillow <dave@...dillows.org>,
Mahesh Bandewar <maheshb@...gle.com>,
Andy Gospodarek <andy@...yhouse.net>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Martin KaFai Lau <martin.lau@...nel.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
Daniel Borkmann <daniel@...earbox.net>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2 net-next v2] bonding: Extending LACP MUX State
Machine to include a Collecting State.
On Thu, Jan 04, 2024 at 05:38:52PM -0800, Jay Vosburgh wrote:
> >+coupled_control
> >+
> >+ Specifies whether the LACP state machine's MUX in the 802.3ad mode
> >+ should have separate Collecting and Distributing states.
> >+
> >+ The default value is 1. This setting does not separate the Collecting
> >+ and Distributing states, maintaining the bond in coupled control.
> >+
>
> Please reference the standard in the description; this is
> implementing the independent control state machine per IEEE 802.1AX-2008
> 5.4.15 in addition to the existing coupled control state machine.
The status of IEEE 802.1AX-2008[1] is "Superseded Standard". Maybe we should
use IEEE 802.1AX-2020[2].
[1] https://standards.ieee.org/ieee/802.1AX/4176/
[2] https://standards.ieee.org/ieee/802.1AX/6768/
Thanks
Hangbin
Powered by blists - more mailing lists