From: patchwork-bot+netdevbpf@kernel.org
To: Jay Vosburgh <jv@jvosburgh.net>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
corbet@lwn.net, andrew+netdev@lunn.ch, linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next] bonding: Remove support for use_carrier
Date: Tue, 02 Sep 2025 23:00:32 +0000 [thread overview]
Message-ID: <175685403232.461360.16040068795389077182.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <2029487.1756512517@famine>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 29 Aug 2025 17:08:37 -0700 you wrote:
> Remove the implementation of use_carrier, the link monitoring
> method that utilizes ethtool or ioctl to determine the link state of an
> interface in a bond. Bonding will always behaves as if use_carrier=1,
> which relies on netif_carrier_ok() to determine the link state of
> interfaces.
>
> To avoid acquiring RTNL many times per second, bonding inspects
> link state under RCU, but not under RTNL. However, ethtool
> implementations in drivers may sleep, and therefore this strategy is
> unsuitable for use with calls into driver ethtool functions.
>
> [...]
Here is the summary with links:
- [net-next] bonding: Remove support for use_carrier
https://git.kernel.org/netdev/net-next/c/23a6037ce76c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-09-02 23:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 0:08 [PATCH net-next] bonding: Remove support for use_carrier Jay Vosburgh
2025-09-02 16:11 ` Stanislav Fomichev
2025-09-02 19:56 ` Jay Vosburgh
2025-09-02 20:40 ` Stanislav Fomichev
2025-09-02 20:50 ` Jakub Kicinski
2025-09-03 9:50 ` Nikolay Aleksandrov
2025-09-03 9:53 ` Nikolay Aleksandrov
2025-09-02 23:00 ` patchwork-bot+netdevbpf [this message]
2025-09-03 9:52 ` Nikolay Aleksandrov
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=175685403232.461360.16040068795389077182.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).