From: Stephen Hemminger <stephen@networkplumber.org>
To: Aahil Awatramani <aahila@google.com>
Cc: Mahesh Bandewar <maheshb@google.com>,
David Dillow <dillow@google.com>,
Jay Vosburgh <j.vosburgh@gmail.com>,
David Ahern <dsahern@gmail.com>,
Hangbin Liu <liuhangbin@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH] ip/bond: add coupled_control support
Date: Wed, 24 Jan 2024 17:55:04 -0800 [thread overview]
Message-ID: <20240124175504.088cc8b1@hermes.local> (raw)
In-Reply-To: <20240125003816.1403636-1-aahila@google.com>
On Thu, 25 Jan 2024 00:38:16 +0000
Aahil Awatramani <aahila@google.com> wrote:
> coupled_control specifies whether the LACP state machine's MUX in the
> 802.3ad mode should have separate Collecting and Distributing states per
> IEEE 802.1AX-2008 5.4.15 for coupled and independent control state.
>
> By default this setting is on and does not separate the Collecting and
> Distributing states, maintaining the bond in coupled control. If set off,
> will toggle independent control state machine which will seperate
> Collecting and Distributing states.
>
> Signed-off-by: Aahil Awatramani <aahila@google.com>
> ---
> include/uapi/linux/if_link.h | 1 +
> ip/iplink_bond.c | 26 +++++++++++++++++++++++++-
> 2 files changed, 26 insertions(+), 1 deletion(-)
>
> diff --git a/include/uapi/linux/if_link.h b/include/uapi/linux/if_link.h
> index d17271fb..ff4ceeaf 100644
> --- a/include/uapi/linux/if_link.h
> +++ b/include/uapi/linux/if_link.h
> @@ -1503,6 +1503,7 @@ enum {
> IFLA_BOND_AD_LACP_ACTIVE,
> IFLA_BOND_MISSED_MAX,
> IFLA_BOND_NS_IP6_TARGET,
> + IFLA_BOND_COUPLED_CONTROL,
> __IFLA_BOND_MAX,
> };
This patch needs to be targeted at iproute2-next
Subject should be:
[PATCH iproute2-next] ip/bond: add coupled_control_support
David will pick up the uapi header once the kernel part is merged.
Since it is a boolean option there is on need for on/off style here.
Just use presence of flag to indicate on state.
And use print_null() to indicate presence of flag rather than using print_string.
next prev parent reply other threads:[~2024-01-25 1:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 0:38 [PATCH] ip/bond: add coupled_control support Aahil Awatramani
2024-01-25 1:55 ` Stephen Hemminger [this message]
2024-01-25 18:08 ` David Ahern
2024-01-25 23:11 ` Aahil Awatramani
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=20240124175504.088cc8b1@hermes.local \
--to=stephen@networkplumber.org \
--cc=aahila@google.com \
--cc=dillow@google.com \
--cc=dsahern@gmail.com \
--cc=j.vosburgh@gmail.com \
--cc=liuhangbin@gmail.com \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.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 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).