From: Ido Schimmel <idosch@nvidia.com>
To: netdev@vger.kernel.org, bridge@lists.linux-foundation.org
Cc: petrm@nvidia.com, mlxsw@nvidia.com, razor@blackwall.org,
Ido Schimmel <idosch@nvidia.com>,
edumazet@google.com, roopa@nvidia.com, kuba@kernel.org,
pabeni@redhat.com, davem@davemloft.net
Subject: [Bridge] [PATCH net-next v2 10/11] vxlan: Enable MDB support
Date: Wed, 15 Mar 2023 15:11:54 +0200 [thread overview]
Message-ID: <20230315131155.4071175-11-idosch@nvidia.com> (raw)
In-Reply-To: <20230315131155.4071175-1-idosch@nvidia.com>
Now that the VXLAN MDB control and data paths are in place we can expose
the VXLAN MDB functionality to user space.
Set the VXLAN MDB net device operations to the appropriate functions,
thereby allowing the rtnetlink code to reach the VXLAN driver.
Signed-off-by: Ido Schimmel <idosch@nvidia.com>
Reviewed-by: Nikolay Aleksandrov <razor@blackwall.org>
---
drivers/net/vxlan/vxlan_core.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/net/vxlan/vxlan_core.c b/drivers/net/vxlan/vxlan_core.c
index 8450768d2300..e2e5f5dac7e6 100644
--- a/drivers/net/vxlan/vxlan_core.c
+++ b/drivers/net/vxlan/vxlan_core.c
@@ -3083,6 +3083,9 @@ static const struct net_device_ops vxlan_netdev_ether_ops = {
.ndo_fdb_del = vxlan_fdb_delete,
.ndo_fdb_dump = vxlan_fdb_dump,
.ndo_fdb_get = vxlan_fdb_get,
+ .ndo_mdb_add = vxlan_mdb_add,
+ .ndo_mdb_del = vxlan_mdb_del,
+ .ndo_mdb_dump = vxlan_mdb_dump,
.ndo_fill_metadata_dst = vxlan_fill_metadata_dst,
};
--
2.37.3
next prev parent reply other threads:[~2023-03-15 13:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 13:11 [Bridge] [PATCH net-next v2 00/11] vxlan: Add MDB support Ido Schimmel
2023-03-15 13:11 ` [Bridge] [PATCH net-next v2 01/11] net: Add MDB net device operations Ido Schimmel
2023-03-15 13:11 ` [Bridge] [PATCH net-next v2 02/11] bridge: mcast: Implement " Ido Schimmel
2023-03-15 13:11 ` [Bridge] [PATCH net-next v2 03/11] rtnetlink: bridge: mcast: Move MDB handlers out of bridge driver Ido Schimmel
2023-03-15 13:11 ` [Bridge] [PATCH net-next v2 04/11] rtnetlink: bridge: mcast: Relax group address validation in common code Ido Schimmel
2023-03-15 13:11 ` [Bridge] [PATCH net-next v2 05/11] vxlan: Move address helpers to private headers Ido Schimmel
2023-03-15 13:11 ` [Bridge] [PATCH net-next v2 06/11] vxlan: Expose vxlan_xmit_one() Ido Schimmel
2023-03-15 13:11 ` [Bridge] [PATCH net-next v2 07/11] vxlan: mdb: Add MDB control path support Ido Schimmel
2023-03-15 13:11 ` [Bridge] [PATCH net-next v2 08/11] vxlan: mdb: Add an internal flag to indicate MDB usage Ido Schimmel
2023-03-15 13:11 ` [Bridge] [PATCH net-next v2 09/11] vxlan: Add MDB data path support Ido Schimmel
2023-03-16 8:55 ` Nikolay Aleksandrov
2023-03-15 13:11 ` Ido Schimmel [this message]
2023-03-15 13:11 ` [Bridge] [PATCH net-next v2 11/11] selftests: net: Add VXLAN MDB test Ido Schimmel
2023-03-17 8:30 ` [Bridge] [PATCH net-next v2 00/11] vxlan: Add MDB support patchwork-bot+netdevbpf
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=20230315131155.4071175-11-idosch@nvidia.com \
--to=idosch@nvidia.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.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