From: Matthieu Baerts <matttbe@kernel.org>
To: David Ahern <dsahern@kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: andrew+netdev@lunn.ch, jv@jvosburgh.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, fbl@redhat.com,
andy@greyhouse.net, shemminger@vyatta.com, maheshb@google.com,
jonas.gorski@gmail.com, horms@kernel.org,
Louis Scalbert <louis.scalbert@6wind.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next v5] ip/bond: add lacp_strict support
Date: Wed, 19 Aug 2026 18:46:11 +0200 [thread overview]
Message-ID: <fc98de42-02cb-4de9-8986-b77414793df5@kernel.org> (raw)
In-Reply-To: <20260625114216.2507435-1-louis.scalbert@6wind.com>
Hi David, Stephen,
On 25/06/2026 13:42, Louis Scalbert wrote:
> lacp_strict defines the behavior of a LACP bonding interface
> when no slaves are in Collecting_Distributing state while at least
> 'min_links' slaves have carrier.
>
> In the default (off) mode, the bonding master remains up and a
> single slave is selected for TX/RX, while traffic received on other
> slaves is dropped. This preserves the existing behavior.
>
> In lacp_strict mode, the bonding master reports carrier down in this
> situation.
I'm sorry to ping you about this, but I'm wondering if this patch has
not been archived on Patchwork by mistake:
https://patchwork.kernel.org/project/netdevbpf/patch/20260625114216.2507435-1-louis.scalbert@6wind.com/
I didn't see any reviews on this v5, and there is no v6: is there
something to fix?
> Link: https://lore.kernel.org/netdev/20260603150331.1919611-1-louis.scalbert@6wind.com/
I'm asking, because this patch is required to execute the
drivers/net/bonding selftests target from 7.2 released this WE.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-08-19 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 11:42 [PATCH iproute2-next v5] ip/bond: add lacp_strict support Louis Scalbert
2026-08-19 16:46 ` Matthieu Baerts [this message]
2026-08-20 7:58 ` Louis Scalbert
2026-08-20 8:44 ` Hangbin Liu
2026-08-20 8:55 ` Hangbin Liu
2026-08-20 16:44 ` Louis Scalbert
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=fc98de42-02cb-4de9-8986-b77414793df5@kernel.org \
--to=matttbe@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andy@greyhouse.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fbl@redhat.com \
--cc=horms@kernel.org \
--cc=jonas.gorski@gmail.com \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=louis.scalbert@6wind.com \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shemminger@vyatta.com \
--cc=stephen@networkplumber.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.