From: Florian Fainelli <f.fainelli@gmail.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/3] net: dsa: add support for bridge flags
Date: Sun, 17 Feb 2019 14:07:54 -0800 [thread overview]
Message-ID: <0f607109-c037-2b7f-cf66-845ce4e7bf33@gmail.com> (raw)
In-Reply-To: <20190217220439.zqu7dz7kfukssrlz@shell.armlinux.org.uk>
On 2/17/2019 2:04 PM, Russell King - ARM Linux admin wrote:
> On Sun, Feb 17, 2019 at 01:37:19PM -0800, Florian Fainelli wrote:
>>
>>
>> On 2/17/2019 6:25 AM, Russell King wrote:
>>> The Linux bridge implementation allows various properties of the bridge
>>> to be controlled, such as flooding unknown unicast and multicast frames.
>>> This patch adds the necessary DSA infrastructure to allow the Linux
>>> bridge support to control these properties for DSA switches.
>>>
>>> We implement this by providing two new methods: one to get the switch-
>>> wide support bitmask, and another to set the properties.
>>>
>>> Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
>>> ---
>>
>> [snip]
>>
>>>
>>> +int dsa_port_bridge_flags(const struct dsa_port *dp, unsigned long flags,
>>> + struct switchdev_trans *trans)
>>> +{
>>> + struct dsa_switch *ds = dp->ds;
>>> + int port = dp->index;
>>> +
>>> + if (switchdev_trans_ph_prepare(trans))
>>> + return ds->ops->port_bridge_flags ? 0 : -EOPNOTSUPP;
>>> +
>>> + if (ds->ops->port_bridge_flags)
>>> + ds->ops->port_bridge_flags(ds, port, flags);
>>
>> If you have a switch fabric with multiple switches, it seems to me that
>> you also need to make sure that the DSA and CPU ports will have
>> compatible flooding attribute, so just like the port_vlan_add()
>> callback, you probably need to make this a switch fabric-wide event and
>> use a notifier here. At least the DSA ports need to have MC flooding
>> turned on for an user port to also have MC flooding working.
>
> mv88e6xxx already today detects CPU and DSA ports and sets unicast
> and multicast flooding for these ports - see
> mv88e6xxx_setup_egress_floods():
Indeed, probably for historical reasons, since that type of logic should
ideally be migrated to the core DSA layer, this is fine for now though.
>
> /* Upstream ports flood frames with unknown unicast or multicast DA */
> flood = dsa_is_cpu_port(ds, port) || dsa_is_dsa_port(ds, port);
> if (chip->info->ops->port_set_egress_floods)
> return chip->info->ops->port_set_egress_floods(chip, port,
> flood, flood);
>
--
Florian
next prev parent reply other threads:[~2019-02-17 22:08 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 [this message]
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
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=0f607109-c037-2b7f-cf66-845ce4e7bf33@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--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).