From: Ido Schimmel <idosch@idosch.org>
To: Mattias Forsblad <mattias.forsblad@gmail.com>
Cc: netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vivien Didelot <vivien.didelot@gmail.com>,
Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Mattias Forsblad <mattias.forsblad+netdev@gmail.com>
Subject: Re: [PATCH 1/3] net: bridge: Implement bridge flag local_receive
Date: Tue, 1 Mar 2022 18:43:27 +0200 [thread overview]
Message-ID: <Yh5NL1SY7+3rLW5O@shredder> (raw)
In-Reply-To: <20220301123104.226731-2-mattias.forsblad+netdev@gmail.com>
On Tue, Mar 01, 2022 at 01:31:02PM +0100, Mattias Forsblad wrote:
> This patch implements the bridge flag local_receive. When this
> flag is cleared packets received on bridge ports will not be forwarded up.
> This makes is possible to only forward traffic between the port members
> of the bridge.
>
> Signed-off-by: Mattias Forsblad <mattias.forsblad+netdev@gmail.com>
> ---
> include/linux/if_bridge.h | 6 ++++++
> include/net/switchdev.h | 2 ++
Nik might ask you to split the offload part from the bridge
implementation. Please wait for his feedback as he might be AFK right
now
> include/uapi/linux/if_bridge.h | 1 +
> include/uapi/linux/if_link.h | 1 +
> net/bridge/br.c | 18 ++++++++++++++++++
> net/bridge/br_device.c | 1 +
> net/bridge/br_input.c | 3 +++
> net/bridge/br_ioctl.c | 1 +
> net/bridge/br_netlink.c | 14 +++++++++++++-
> net/bridge/br_private.h | 2 ++
> net/bridge/br_sysfs_br.c | 23 +++++++++++++++++++++++
I believe the bridge doesn't implement sysfs for new attributes
> net/bridge/br_vlan.c | 8 ++++++++
> 12 files changed, 79 insertions(+), 1 deletion(-)
[...]
> diff --git a/net/bridge/br_input.c b/net/bridge/br_input.c
> index e0c13fcc50ed..5864b61157d3 100644
> --- a/net/bridge/br_input.c
> +++ b/net/bridge/br_input.c
> @@ -163,6 +163,9 @@ int br_handle_frame_finish(struct net *net, struct sock *sk, struct sk_buff *skb
> break;
> }
>
> + if (local_rcv && !br_opt_get(br, BROPT_LOCAL_RECEIVE))
> + local_rcv = false;
> +
I don't think the description in the commit message is accurate:
"packets received on bridge ports will not be forwarded up". From the
code it seems that if packets hit a local FDB entry, then they will be
"forwarded up". Instead, it seems that packets will not be flooded
towards the bridge. In which case, why not maintain the same granularity
we have for the rest of the ports and split this into unicast /
multicast / broadcast?
BTW, while the patch honors local FDB entries, it overrides host MDB
entries which seems wrong / inconsistent.
> if (dst) {
> unsigned long now = jiffies;
next prev parent reply other threads:[~2022-03-01 16:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 12:31 [PATCH net-next 0/3] bridge: dsa: switchdev: mv88e6xxx: Implement local_receive bridge flag Mattias Forsblad
2022-03-01 12:31 ` [PATCH 1/3] net: bridge: Implement bridge flag local_receive Mattias Forsblad
2022-03-01 16:43 ` Ido Schimmel [this message]
2022-03-01 22:36 ` Nikolay Aleksandrov
2022-03-02 6:27 ` Mattias Forsblad
2022-03-14 16:29 ` Ido Schimmel
2022-03-14 16:33 ` Ido Schimmel
2022-03-14 16:48 ` Mattias Forsblad
2022-03-02 3:25 ` Roopa Prabhu
2022-03-01 22:43 ` Nikolay Aleksandrov
2022-03-02 6:33 ` Mattias Forsblad
2022-03-02 6:38 ` Mattias Forsblad
2022-03-01 12:31 ` [PATCH 2/3] dsa: Handle the local_receive flag in the DSA layer Mattias Forsblad
2022-03-01 12:31 ` [PATCH 3/3] mv88e6xxx: Offload the local_receive flag Mattias Forsblad
2022-03-02 12:19 ` kernel test robot
2022-03-02 13:30 ` kernel test robot
2022-03-01 17:14 ` [PATCH net-next 0/3] bridge: dsa: switchdev: mv88e6xxx: Implement local_receive bridge flag Florian Fainelli
2022-03-01 21:04 ` Tobias Waldekranz
2022-03-17 14:05 ` Vladimir Oltean
2022-03-18 7:58 ` Tobias Waldekranz
2022-03-18 11:11 ` Vladimir Oltean
2022-03-18 12:09 ` Tobias Waldekranz
2022-03-18 12:44 ` Vladimir Oltean
2022-03-18 16:03 ` Tobias Waldekranz
2022-03-18 16:26 ` Vladimir Oltean
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=Yh5NL1SY7+3rLW5O@shredder \
--to=idosch@idosch.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=mattias.forsblad+netdev@gmail.com \
--cc=mattias.forsblad@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=vivien.didelot@gmail.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