From: Joseph Huang <Joseph.Huang@garmin.com>
To: <netdev@vger.kernel.org>
Cc: Joseph Huang <Joseph.Huang@garmin.com>,
Joseph Huang <joseph.huang.2024@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Simon Horman <horms@kernel.org>, <linux-kernel@vger.kernel.org>,
<bridge@lists.linux.dev>
Subject: [Patch v2 net-next 0/3] Add support for mdb offload failure notification
Date: Thu, 3 Apr 2025 19:44:02 -0400 [thread overview]
Message-ID: <20250403234412.1531714-1-Joseph.Huang@garmin.com> (raw)
Currently the bridge does not provide real-time feedback to user space
on whether or not an attempt to offload an mdb entry was successful.
This patch set adds support to notify user space about failed offload
attempts, and is controlled by a new knob mdb_offload_fail_notification.
A break-down of the patches in the series:
Patch 1 adds offload failed flag to indicate that the offload attempt
has failed. The flag is reflected in netlink mdb entry flags.
Patch 2 adds the new bridge bool option mdb_offload_fail_notification.
Patch 3 notifies user space when the result is known, controlled by
mdb_offload_fail_notification setting.
Joseph Huang (3):
net: bridge: mcast: Add offload failed mdb flag
net: bridge: Add offload_fail_notification bopt
net: bridge: mcast: Notify on mdb offload failure
include/uapi/linux/if_bridge.h | 10 ++++++----
net/bridge/br.c | 5 +++++
net/bridge/br_mdb.c | 28 +++++++++++++++++++++++-----
net/bridge/br_private.h | 30 +++++++++++++++++++++++++-----
net/bridge/br_switchdev.c | 11 ++++++-----
5 files changed, 65 insertions(+), 19 deletions(-)
---
v1: https://lore.kernel.org/netdev/20250318224255.143683-1-Joseph.Huang@garmin.com/
iproute2 link:
https://lore.kernel.org/netdev/20250318225026.145501-1-Joseph.Huang@garmin.com/
v2: Add br_multicast_pg_set_offload_flags helper to set offload flags
Change multi-valued option mdb_notify_on_flag_change to bool option
mdb_offload_fail_notification
Change _br_mdb_notify to __br_mdb_notify
Drop all #ifdef CONFIG_NET_SWITCHDEV
Add br_mdb_should_notify helper and reorganize code in
br_switch_mdb_complete
--
2.49.0
next reply other threads:[~2025-04-03 23:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 23:44 Joseph Huang [this message]
2025-04-03 23:44 ` [Patch v2 net-next 1/3] net: bridge: mcast: Add offload failed mdb flag Joseph Huang
2025-04-04 10:30 ` Nikolay Aleksandrov
2025-04-03 23:44 ` [Patch v2 net-next 2/3] net: bridge: Add offload_fail_notification bopt Joseph Huang
2025-04-04 10:30 ` Nikolay Aleksandrov
2025-04-03 23:44 ` [Patch v2 net-next 3/3] net: bridge: mcast: Notify on mdb offload failure Joseph Huang
2025-04-04 10:29 ` Nikolay Aleksandrov
2025-04-04 15:25 ` Joseph Huang
2025-04-04 20:04 ` Nikolay Aleksandrov
2025-04-04 20:11 ` Joseph Huang
2025-04-04 20:15 ` 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=20250403234412.1531714-1-Joseph.Huang@garmin.com \
--to=joseph.huang@garmin.com \
--cc=andrew+netdev@lunn.ch \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=joseph.huang.2024@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.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