From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>
Cc: <UNGLinuxDriver@microchip.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<linux@armlinux.org.uk>,
Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: [PATCH net-next 6/8] net: lan966x: Extend FDB to support also lag
Date: Sun, 26 Jun 2022 15:04:49 +0200 [thread overview]
Message-ID: <20220626130451.1079933-7-horatiu.vultur@microchip.com> (raw)
In-Reply-To: <20220626130451.1079933-1-horatiu.vultur@microchip.com>
Offload FDB entries when the original device is a lag interface. Because
all the ports under the lag have the same chip id, which is the chip id
of first port, then add the entries only for the first port.
Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
---
.../ethernet/microchip/lan966x/lan966x_fdb.c | 31 +++++++++++++++++++
.../ethernet/microchip/lan966x/lan966x_lag.c | 16 ++++++++++
.../ethernet/microchip/lan966x/lan966x_main.h | 7 +++++
3 files changed, 54 insertions(+)
diff --git a/drivers/net/ethernet/microchip/lan966x/lan966x_fdb.c b/drivers/net/ethernet/microchip/lan966x/lan966x_fdb.c
index 2e186e9d9893..154efbd0c319 100644
--- a/drivers/net/ethernet/microchip/lan966x/lan966x_fdb.c
+++ b/drivers/net/ethernet/microchip/lan966x/lan966x_fdb.c
@@ -194,6 +194,35 @@ static void lan966x_fdb_bridge_event_work(struct lan966x_fdb_event_work *fdb_wor
}
}
+static void lan966x_fdb_lag_event_work(struct lan966x_fdb_event_work *fdb_work)
+{
+ struct switchdev_notifier_fdb_info *fdb_info;
+ struct lan966x_port *port;
+ struct lan966x *lan966x;
+
+ if (!lan966x_lag_first_port(fdb_work->orig_dev, fdb_work->dev))
+ return;
+
+ lan966x = fdb_work->lan966x;
+ port = netdev_priv(fdb_work->dev);
+ fdb_info = &fdb_work->fdb_info;
+
+ switch (fdb_work->event) {
+ case SWITCHDEV_FDB_ADD_TO_DEVICE:
+ if (!fdb_info->added_by_user)
+ break;
+ lan966x_lag_mac_add_entry(lan966x, port, fdb_info->addr,
+ fdb_info->vid);
+ break;
+ case SWITCHDEV_FDB_DEL_TO_DEVICE:
+ if (!fdb_info->added_by_user)
+ break;
+ lan966x_lag_mac_del_entry(lan966x, fdb_info->addr,
+ fdb_info->vid);
+ break;
+ }
+}
+
static void lan966x_fdb_event_work(struct work_struct *work)
{
struct lan966x_fdb_event_work *fdb_work =
@@ -203,6 +232,8 @@ static void lan966x_fdb_event_work(struct work_struct *work)
lan966x_fdb_port_event_work(fdb_work);
else if (netif_is_bridge_master(fdb_work->orig_dev))
lan966x_fdb_bridge_event_work(fdb_work);
+ else if (netif_is_lag_master(fdb_work->orig_dev))
+ lan966x_fdb_lag_event_work(fdb_work);
kfree(fdb_work->fdb_info.addr);
dev_put(fdb_work->orig_dev);
diff --git a/drivers/net/ethernet/microchip/lan966x/lan966x_lag.c b/drivers/net/ethernet/microchip/lan966x/lan966x_lag.c
index c721a05d44d2..db21bd358e4e 100644
--- a/drivers/net/ethernet/microchip/lan966x/lan966x_lag.c
+++ b/drivers/net/ethernet/microchip/lan966x/lan966x_lag.c
@@ -294,3 +294,19 @@ u32 lan966x_lag_get_mask(struct lan966x *lan966x, struct net_device *bond,
return mask;
}
+
+void lan966x_lag_mac_del_entry(struct lan966x *lan966x,
+ const unsigned char *addr,
+ u16 vid)
+{
+ lan966x_mac_del_entry(lan966x, addr, vid);
+}
+
+int lan966x_lag_mac_add_entry(struct lan966x *lan966x,
+ struct lan966x_port *port,
+ const unsigned char *addr,
+ u16 vid)
+{
+ lan966x_mac_del_entry(lan966x, addr, vid);
+ return lan966x_mac_add_entry(lan966x, port, addr, vid);
+}
diff --git a/drivers/net/ethernet/microchip/lan966x/lan966x_main.h b/drivers/net/ethernet/microchip/lan966x/lan966x_main.h
index 2c382cf8fe3a..7b4805813549 100644
--- a/drivers/net/ethernet/microchip/lan966x/lan966x_main.h
+++ b/drivers/net/ethernet/microchip/lan966x/lan966x_main.h
@@ -426,6 +426,13 @@ int lan966x_lag_netdev_changeupper(struct net_device *dev,
bool lan966x_lag_first_port(struct net_device *lag, struct net_device *dev);
u32 lan966x_lag_get_mask(struct lan966x *lan966x, struct net_device *bond,
bool only_active_ports);
+void lan966x_lag_mac_del_entry(struct lan966x *lan966x,
+ const unsigned char *addr,
+ u16 vid);
+int lan966x_lag_mac_add_entry(struct lan966x *lan966x,
+ struct lan966x_port *port,
+ const unsigned char *addr,
+ u16 vid);
int lan966x_port_changeupper(struct net_device *dev,
struct net_device *brport_dev,
--
2.33.0
next prev parent reply other threads:[~2022-06-26 13:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 13:04 [PATCH net-next 0/8] net: lan966x: Add lag support Horatiu Vultur
2022-06-26 13:04 ` [PATCH net-next 1/8] net: lan966x: Add reqisters used to configure lag interfaces Horatiu Vultur
2022-06-26 13:04 ` [PATCH net-next 2/8] net: lan966x: Split lan966x_fdb_event_work Horatiu Vultur
2022-06-26 13:04 ` [PATCH net-next 3/8] net: lan966x: Expose lan966x_switchdev_nb and lan966x_switchdev_blocking_nb Horatiu Vultur
2022-06-26 13:04 ` [PATCH net-next 4/8] net: lan966x: Extend lan966x_foreign_bridging_check Horatiu Vultur
2022-06-26 13:04 ` [PATCH net-next 5/8] net: lan966x: Add lag support for lan966x Horatiu Vultur
2022-06-26 14:11 ` Vladimir Oltean
2022-06-27 6:46 ` Horatiu Vultur
2022-06-27 9:40 ` Vladimir Oltean
2022-06-26 13:04 ` Horatiu Vultur [this message]
2022-06-26 13:04 ` [PATCH net-next 7/8] net: lan966x: Extend MAC to support also lag interfaces Horatiu Vultur
2022-06-26 13:04 ` [PATCH net-next 8/8] net: lan966x: Update PGID when lag ports are changing link status Horatiu Vultur
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=20220626130451.1079933-7-horatiu.vultur@microchip.com \
--to=horatiu.vultur@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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