From: Florian Fainelli <f.fainelli@gmail.com>
To: Mattias Forsblad <mattias.forsblad@gmail.com>, netdev@vger.kernel.org
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Mattias Forsblad <mattias.forsblad+netdev@gmail.com>,
Tobias Waldekranz <tobias@waldekranz.com>
Subject: Re: [PATCH net-next 0/3] bridge: dsa: switchdev: mv88e6xxx: Implement local_receive bridge flag
Date: Tue, 1 Mar 2022 09:14:20 -0800 [thread overview]
Message-ID: <2d38e998-396f-db39-7ccf-2a991d4e02cb@gmail.com> (raw)
In-Reply-To: <20220301123104.226731-1-mattias.forsblad+netdev@gmail.com>
On 3/1/2022 4:31 AM, Mattias Forsblad wrote:
> Greetings,
>
> This series implements a new bridge flag 'local_receive' and HW
> offloading for Marvell mv88e6xxx.
>
> When using a non-VLAN filtering bridge we want to be able to limit
> traffic to the CPU port to lessen the CPU load. This is specially
> important when we have disabled learning on user ports.
>
> A sample configuration could be something like this:
>
> br0
> / \
> swp0 swp1
>
> ip link add dev br0 type bridge stp_state 0 vlan_filtering 0
> ip link set swp0 master br0
> ip link set swp1 master br0
> ip link set swp0 type bridge_slave learning off
> ip link set swp1 type bridge_slave learning off
> ip link set swp0 up
> ip link set swp1 up
> ip link set br0 type bridge local_receive 0
> ip link set br0 up
>
> The first part of the series implements the flag for the SW bridge
> and the second part the DSA infrastructure. The last part implements
> offloading of this flag to HW for mv88e6xxx, which uses the
> port vlan table to restrict the ingress from user ports
> to the CPU port when this flag is cleared.
Why not use a bridge with VLAN filtering enabled? I cannot quite find it
right now, but Vladimir recently picked up what I had attempted before
which was to allow removing the CPU port (via the bridge master device)
from a specific group of VLANs to achieve that isolation.
>
> Reviewed-by: Tobias Waldekranz <tobias@waldekranz.com>
I don't believe this tag has much value since it was presumably carried
over from an internal review. Might be worth adding it publicly now, though.
>
> Regards,
> Mattias Forsblad (3):
> net: bridge: Implement bridge flag local_receive
> dsa: Handle the local_receive flag in the DSA layer.
> mv88e6xxx: Offload the local_receive flag
>
> drivers/net/dsa/mv88e6xxx/chip.c | 45 ++++++++++++++++++++++++++++++--
> include/linux/if_bridge.h | 6 +++++
> include/net/dsa.h | 6 +++++
> include/net/switchdev.h | 2 ++
> 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 ++++++++++++++++
> net/bridge/br_vlan.c | 8 ++++++
> net/dsa/dsa_priv.h | 1 +
> net/dsa/slave.c | 16 ++++++++++++
> 16 files changed, 145 insertions(+), 3 deletions(-)
>
--
Florian
next prev parent reply other threads:[~2022-03-01 17:14 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
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 ` Florian Fainelli [this message]
2022-03-01 21:04 ` [PATCH net-next 0/3] bridge: dsa: switchdev: mv88e6xxx: Implement local_receive bridge flag 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=2d38e998-396f-db39-7ccf-2a991d4e02cb@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--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=tobias@waldekranz.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).