From: Vivien Didelot <vivien.didelot@gmail.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 2/3] net: dsa: mv88e6xxx: add support for bridge flags
Date: Tue, 19 Feb 2019 12:38:28 -0500 [thread overview]
Message-ID: <20190219123828.GD10959@t480s.localdomain> (raw)
In-Reply-To: <20190219171414.cvaiw7u2xnd5zk3g@shell.armlinux.org.uk>
Hi Russell,
On Tue, 19 Feb 2019 17:14:14 +0000, Russell King - ARM Linux admin <linux@armlinux.org.uk> wrote:
> > > > > +static unsigned long mv88e6xxx_bridge_flags_support(struct dsa_switch *ds)
> > > > > +{
> > > > > + struct mv88e6xxx_chip *chip = ds->priv;
> > > > > + unsigned long support = 0;
> > > > > +
> > > > > + if (chip->info->ops->port_set_egress_floods)
> > > > > + support |= BR_FLOOD | BR_MCAST_FLOOD;
> > > > > +
> > > > > + return support;
> > > > > +}
> > > >
> > > > I think that it isn't necessary to propagate the notion of bridge flags down
> > > > to the DSA drivers. It might be just enough to add:
> > > >
> > > > port_egress_flood(dsa_switch *ds, int port, bool uc, bool mc)
> > > >
> > > > to dsa_switch_ops and set BR_FLOOD | BR_MCAST_FLOOD from the DSA core,
> > > > if the targeted driver has ds->ops->port_set_egress_flood. What do you think?
> > >
> > > There are two other flags that I haven't covered which the bridge code
> > > expects to be offloaded, and those are the broadcast flood flag and
> > > the learning flag.
> >
> > I see. What does the bridge code do if these flags are set? Does it expect
> > the underlying devices to handle ff:ff:ff:ff:ff:ff magically or does it
> > program this entry into the bridged ports?
>
> The bridge code defaults to all four flags set. See new_nbp() in
> net/bridge/br_if.c:
>
> p->flags = BR_LEARNING | BR_FLOOD | BR_MCAST_FLOOD | BR_BCAST_FLOOD;
>
> bridge(8) doesn't touch BR_BCAST_FLOOD, but it is made available to
> userspace via netlink and IFLA_BRPORT_BCAST_FLOOD. Hence, there's
> no man page documentation for that flag.
>
> According to br_flood() in net/bridge/br_forward.c, it controls
> whether broadcast frames are flooded to all ports or not. Changing
> this flag is merely handled just like the multicast/unicast flooding
> flags - a call is made to set the offloaded flags, and if it isn't
> returned as being supported, a warning is printed. No attempt is
> made to create or change a forwarding entry for the broadcast MAC
> address.
OK, thanks for the details. The programming of the broadcast MAC address
must be handled in the core then, I will move this from mv88e6xxx up to the
DSA layer later, but that's totally orthogonal here.
>
> bridge(8) does document BR_LEARNING via IFLA_BRPORT_LEARNING:
>
> learning on or learning off
> Controls whether a given port will learn MAC addresses from
> received traffic or not. If learning if off, the bridge will end
> up flooding any traffic for which it has no FDB entry. By
> default this flag is on.
>
> > In the latter case we have almost nothing to do. In the former case, we can
> > make the core call dsa_port_mdb_add on setup and when a VLAN is added.
> >
> > mv88e6xxx tries to be smart and is already doing that and I'm really not a fan.
> >
> > If tomorrow there's a switch capable of simply toggling a bit to do that,
> > we can add a new ops and skip the port_mdb_add call in the core.
> >
> > > I know that the Marvell switches don't have a bit to control the
> > > broadcast flooding, that appears to be controlled via a static entry
> > > in the ATU which would have to be modified as the broadcast flood flag
> > > is manipulated. I don't know how that is handled in other bridges.
> > >
> > > Do we want to include the broadcast flood in the above prototype?
> > > If we go for this, how do we detect which options a switch supports?
> >
> > If the necessary dsa_switch_ops routine is correctly prototyped, having it
> > implemented by a driver or not should be enough to inform the core that the
> > related feature(s) is/are supported by the switch.
> >
> > I'll try to give a bit more context on why I'd prefer this approach, hoping
> > it makes sense: a switch driver does not need to understand bridge flags
> > per-se, the core should give enough abstraction to this layer (and any other
> > net-specifics). The core just needs to know if a driver can program this or
> > that. More importantly, it can easily become messy to maintain switch-cases
> > of arbitrary flags in all drivers and the core.
>
> So, should we go the other way and have:
>
> int (*port_learning)(struct dsa_switch *ds, int port, bool enable);
> int (*port_egress_flood_uc)(struct dsa_switch *ds, int port, bool enable);
> int (*port_egress_flood_mc)(struct dsa_switch *ds, int port, bool enable);
> int (*port_egress_flood_bc)(struct dsa_switch *ds, int port, bool enable);
>
> rather than trying to combine uc/mc into one? It would mean that we'd
> be performing more bus reads/writes, but I guess that doesn't matter
> for these configuration parameters.
I like this very much. As long as these flags can be programmed in switch
devices, these ops totally make sense.
Thanks,
Vivien
next prev parent reply other threads:[~2019-02-19 17:38 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 14:24 [PATCH net-next 0/3] net: dsa: mv88e6xxx: fix IPv6 Russell King - ARM Linux admin
2019-02-17 14:25 ` [PATCH net-next 1/3] net: dsa: add support for bridge flags Russell King
2019-02-17 21:37 ` Florian Fainelli
2019-02-17 22:04 ` Russell King - ARM Linux admin
2019-02-17 22:07 ` Florian Fainelli
2019-02-18 0:50 ` Russell King - ARM Linux admin
2019-02-18 11:23 ` Russell King - ARM Linux admin
2019-02-19 15:42 ` Vivien Didelot
2019-02-17 14:25 ` [PATCH net-next 2/3] net: dsa: mv88e6xxx: " Russell King
2019-02-17 21:38 ` Florian Fainelli
2019-02-17 14:25 ` [PATCH net-next 3/3] net: dsa: mv88e6xxx: defautl to multicast and unicast flooding Russell King
2019-02-17 14:27 ` Russell King - ARM Linux admin
2019-02-17 16:34 ` Russell King - ARM Linux admin
2019-02-17 21:45 ` Florian Fainelli
2019-02-17 21:58 ` Russell King - ARM Linux admin
2019-02-17 22:03 ` Florian Fainelli
2019-02-17 22:19 ` Russell King - ARM Linux admin
2019-02-17 22:30 ` Florian Fainelli
2019-02-17 16:31 ` [PATCH net-next v2 0/3] net: dsa: mv88e6xxx: fix IPv6 Russell King - ARM Linux admin
2019-02-17 16:32 ` [PATCH net-next v2 1/3] net: dsa: add support for bridge flags Russell King
2019-02-17 16:32 ` [PATCH net-next v2 2/3] net: dsa: mv88e6xxx: " Russell King
2019-02-19 16:16 ` Vivien Didelot
2019-02-19 16:24 ` Russell King - ARM Linux admin
2019-02-19 17:00 ` Vivien Didelot
2019-02-19 17:14 ` Russell King - ARM Linux admin
2019-02-19 17:38 ` Vivien Didelot [this message]
2019-02-19 17:44 ` Florian Fainelli
2019-02-19 18:20 ` Vivien Didelot
2019-02-19 18:08 ` Russell King - ARM Linux admin
2019-02-19 19:04 ` Vivien Didelot
2019-02-19 19:10 ` Russell King - ARM Linux admin
2019-02-19 19:37 ` Florian Fainelli
2019-02-19 19:56 ` Vivien Didelot
2019-02-19 22:52 ` Russell King - ARM Linux admin
2019-02-19 17:00 ` Russell King - ARM Linux admin
2019-02-19 17:23 ` Vivien Didelot
2019-02-19 17:27 ` Russell King - ARM Linux admin
2019-02-19 23:34 ` Russell King - ARM Linux admin
2019-02-19 23:53 ` Florian Fainelli
2019-02-20 0:07 ` Russell King - ARM Linux admin
2019-02-17 16:32 ` [PATCH net-next v2 3/3] net: dsa: mv88e6xxx: default to multicast and unicast flooding Russell King
2019-02-18 12:53 ` Russell King - ARM Linux admin
2019-02-19 16:05 ` Vivien Didelot
2019-02-19 16:18 ` Russell King - ARM Linux admin
2019-02-18 11:34 ` [PATCH net-next v2 0/3] net: dsa: mv88e6xxx: fix IPv6 Russell King - ARM Linux admin
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=20190219123828.GD10959@t480s.localdomain \
--to=vivien.didelot@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.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 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).