From: Tobias Waldekranz <tobias@waldekranz.com>
To: davem@davemloft.net, kuba@kernel.org
Cc: andrew@lunn.ch, vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, roopa@nvidia.com, nikolay@nvidia.com,
netdev@vger.kernel.org
Subject: [RFC net-next 0/7] net: dsa: Sync local bridge FDB addresses to hardware
Date: Sat, 16 Jan 2021 02:25:08 +0100 [thread overview]
Message-ID: <20210116012515.3152-1-tobias@waldekranz.com> (raw)
This is an extension of previous work done by Vladimir Oltean:
https://lore.kernel.org/netdev/20210106095136.224739-1-olteanv@gmail.com/
With this series, local addresses belonging to bridge ports or to the
bridge itself are also synced down to the hardware FDB. As a result
the hardware can avoid flooding return traffic to the CPU which is not
only inefficient but also very confusing to users:
https://lore.kernel.org/netdev/CAGwvh_MAQWuKuhu5VuYjibmyN-FRxCXXhrQBRm34GShZPSN6Aw@mail.gmail.com/
https://lore.kernel.org/netdev/6106e3d5-31fc-388e-d4ac-c84ac0746a72@prevas.dk/
Patch 1 through 3 extends the switchdev fdb notifications to include
the local flag, and to handle the case when an entry is added to the
bridge itself.
Patches 4 through 6 enables DSA to make use of those extensions.
Finally, enable assisted learning on the CPU port for mv88e6xxx.
Tobias Waldekranz (7):
net: bridge: switchdev: Refactor br_switchdev_fdb_notify
net: bridge: switchdev: Include local flag in FDB notifications
net: bridge: switchdev: Send FDB notifications for host addresses
net: dsa: Include local addresses in assisted CPU port learning
net: dsa: Include bridge addresses in assisted CPU port learning
net: dsa: Sync static FDB entries on foreign interfaces to hardware
net: dsa: mv88e6xxx: Request assisted learning on CPU port
drivers/net/dsa/mv88e6xxx/chip.c | 1 +
include/net/switchdev.h | 1 +
net/bridge/br_fdb.c | 4 +--
net/bridge/br_private.h | 7 +++--
net/bridge/br_switchdev.c | 47 ++++++++++----------------------
net/dsa/slave.c | 26 ++++++++++++------
6 files changed, 40 insertions(+), 46 deletions(-)
--
2.17.1
next reply other threads:[~2021-01-16 1:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 1:25 Tobias Waldekranz [this message]
2021-01-16 1:25 ` [RFC net-next 1/7] net: bridge: switchdev: Refactor br_switchdev_fdb_notify Tobias Waldekranz
2021-01-17 17:24 ` Vladimir Oltean
2021-01-16 1:25 ` [RFC net-next 2/7] net: bridge: switchdev: Include local flag in FDB notifications Tobias Waldekranz
2021-01-17 19:30 ` Vladimir Oltean
2021-01-18 18:58 ` Tobias Waldekranz
2021-01-18 19:27 ` Vladimir Oltean
2021-01-18 20:19 ` Tobias Waldekranz
2021-01-18 21:03 ` Vladimir Oltean
2021-01-18 21:17 ` Nikolay Aleksandrov
2021-01-18 21:22 ` Nikolay Aleksandrov
2021-01-18 21:39 ` Nikolay Aleksandrov
2021-01-18 21:50 ` Vladimir Oltean
2021-01-18 21:53 ` Nikolay Aleksandrov
2021-01-18 22:06 ` Vladimir Oltean
2021-01-18 22:09 ` Vladimir Oltean
2021-01-18 22:42 ` Nikolay Aleksandrov
2021-01-19 0:42 ` Vladimir Oltean
2021-01-19 10:14 ` Nikolay Aleksandrov
2021-01-18 19:28 ` Ido Schimmel
2021-01-16 1:25 ` [RFC net-next 3/7] net: bridge: switchdev: Send FDB notifications for host addresses Tobias Waldekranz
2021-01-18 11:28 ` Vladimir Oltean
2021-01-16 1:25 ` [RFC net-next 4/7] net: dsa: Include local addresses in assisted CPU port learning Tobias Waldekranz
2021-01-16 1:25 ` [RFC net-next 5/7] net: dsa: Include bridge " Tobias Waldekranz
2021-01-16 1:25 ` [RFC net-next 6/7] net: dsa: Sync static FDB entries on foreign interfaces to hardware Tobias Waldekranz
2021-01-16 1:25 ` [RFC net-next 7/7] net: dsa: mv88e6xxx: Request assisted learning on CPU port Tobias Waldekranz
2021-02-01 6:24 ` DENG Qingfang
2021-02-03 9:27 ` Tobias Waldekranz
2021-02-03 10:14 ` Vladimir Oltean
2021-02-03 10:42 ` Tobias Waldekranz
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=20210116012515.3152-1-tobias@waldekranz.com \
--to=tobias@waldekranz.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=olteanv@gmail.com \
--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).