From: Ido Schimmel <idosch@idosch.org>
To: mattias.forsblad+netdev@gmail.com
Cc: Nikolay Aleksandrov <razor@blackwall.org>,
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>
Subject: Re: [PATCH 1/3] net: bridge: Implement bridge flag local_receive
Date: Mon, 14 Mar 2022 18:33:32 +0200 [thread overview]
Message-ID: <Yi9uXGnrrOT13kiI@shredder> (raw)
In-Reply-To: <Yi9tgOQ32q2l2TxD@shredder>
On Mon, Mar 14, 2022 at 06:29:58PM +0200, Ido Schimmel wrote:
> On Wed, Mar 02, 2022 at 07:27:25AM +0100, Mattias Forsblad wrote:
> > On 2022-03-01 23:36, Nikolay Aleksandrov wrote:
> > > On 1 March 2022 17:43:27 CET, Ido Schimmel <idosch@idosch.org> wrote:
> > >> On Tue, Mar 01, 2022 at 01:31:02PM +0100, Mattias Forsblad wrote:
> > >>> 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?
> > >>
> > >
> > > Exactly my first thought - why not implement the same control for the bridge?
> > > Also try to minimize the fast-path hit, you can keep the needed changes
> > > localized only to the cases where they are needed.
> > > I'll send a few more comments in a reply to the patch.
> > >
> >
> > Soo, if I understand you correctly, you want to have three different options?
> > local_receive_unicast
> > local_receive_multicast
> > local_receive_broadcast
>
> My understanding of the feature is that you want to prevent flooding
> towards the bridge. In which case, it makes sense to keep the same
> granularity as for regular bridge ports and also name the options
> similarly. We already have several options that are applicable to both
> the bridge and bridge ports (e.g., 'mcast_router').
>
> I suggest:
>
> $ ip link help bridge
> Usage: ... bridge [ fdb_flush ]
> ...
> [ flood {on | off} ]
> [ mcast_flood {on | off} ]
> [ bcast_flood {on | off} ]
>
> This is consistent with "bridge_slave".
And please add a selftest. See this commit for reference:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b2b681a412517bf477238de62b1d227361fa04fe
It should allow you to test both the software data path (using veth
pairs) and the hardware data path (using physical loopbacks).
next prev parent reply other threads:[~2022-03-14 16:33 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
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 [this message]
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=Yi9uXGnrrOT13kiI@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=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;
as well as URLs for NNTP newsgroup(s).