Changes in Makefile

a3a48de5 - vxlan: mdb: Add MDB control path support

Wed, 15 Mar 2023 13:11:51 +0000

vxlan: mdb: Add MDB control path supportImplement MDB control path support, enabling the creation, deletion,replacement and dumping of MDB entries in a similar fashion to thebridge driver. Unlike the bridge driver, each entry stores a list ofremote VTEPs to which matched packets need to be replicated to and not alist of bridge ports.The motivating use case is the installation of MDB entries by a userspace control plane in response to received EVPN routes. As such, onlyallow permanent MDB entries to be installed and do not implementsnooping functionality, avoiding a lot of unnecessary complexity.Since entries can only be modified by user space under RTNL, use RTNL asthe write lock. Use RCU to ensure that MDB entries and remotes are notfreed while being accessed from the data path during transmission.In terms of uAPI, reuse the existing MDB netlink interface, but add afew new attributes to request and response messages:* IP address of the destination VXLAN tunnel endpoint where the multicast receivers reside.* UDP destination port number to use to connect to the remote VXLAN tunnel endpoint.* VXLAN VNI Network Identifier to use to connect to the remote VXLAN tunnel endpoint. Required when Ingress Replication (IR) is used and the remote VTEP is not a member of originating broadcast domain (VLAN/VNI) [1].* Source VNI Network Identifier the MDB entry belongs to. Used only when the VXLAN device is in external mode.* Interface index of the outgoing interface to reach the remote VXLAN tunnel endpoint. This is required when the underlay destination IP is multicast (P2MP), as the multicast routing tables are not consulted.All the new attributes are added under the 'MDBA_SET_ENTRY_ATTRS' nestwhich is strictly validated by the bridge driver, thereby automaticallyrejecting the new attributes.[1] https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-irb-mcast#section-3.2.2Signed-off-by: Ido Schimmel Reviewed-by: Nikolay Aleksandrov Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/vxlan/Makefile

f9c4bb0b - vxlan: vni filtering support on collect metadata device

Tue, 01 Mar 2022 05:04:36 +0000

vxlan: vni filtering support on collect metadata deviceThis patch adds vnifiltering support to collect metadata device.Motivation:You can only use a single vxlan collect metadata device for a givenvxlan udp port in the system today. The vxlan collect metadata deviceterminates all received vxlan packets. As shown in the below diagram,there are use-cases where you need to support multiple such vxlan devices inindependent bridge domains. Each vxlan device must terminate the vni'sit is configured for.Example usecase: In a service provider network a service providertypically supports multiple bridge domains with overlapping vlans.One bridge domain per customer. Vlans in each bridge domain aremapped to globally unique vxlan ranges assigned to each customer.vnifiltering support in collect metadata devices terminates only configuredvnis. This is similar to vlan filtering in bridge driver. The vni filteringcapability is provided by a new flag on collect metadata device.In the below pic: - customer1 is mapped to br1 bridge domain - customer2 is mapped to br2 bridge domain - customer1 vlan 10-11 is mapped to vni 1001-1002 - customer2 vlan 10-11 is mapped to vni 2001-2002 - br1 and br2 are vlan filtering bridges - vxlan1 and vxlan2 are collect metadata devices with vnifiltering enabled┌──────────────────────────────────────────────────────────────────┐│ switch ││ ││ ┌───────────┐ ┌───────────┐ ││ │ │ │ │ ││ │ br1 │ │ br2 │ ││ └┬─────────┬┘ └──┬───────┬┘ ││ vlans│ │ vlans │ │ ││ 10,11│ │ 10,11│ │ ││ │ vlanvnimap: │ vlanvnimap: ││ │ 10-1001,11-1002 │ 10-2001,11-2002 ││ │ │ │ │ ││ ┌──────┴┐ ┌──┴─────────┐ ┌───┴────┐ │ ││ │ swp1 │ │vxlan1 │ │ swp2 │ ┌┴─────────────┐ ││ │ │ │ vnifilter:│ │ │ │vxlan2 │ ││ └───┬───┘ │ 1001,1002│ └───┬────┘ │ vnifilter: │ ││ │ └────────────┘ │ │ 2001,2002 │ ││ │ │ └──────────────┘ ││ │ │ │└───────┼──────────────────────────────────┼───────────────────────┘ │ │ │ │ ┌─────┴───────┐ │ │ customer1 │ ┌─────┴──────┐ │ host/VM │ │customer2 │ └─────────────┘ │ host/VM │ └────────────┘With this implementation, vxlan dst metadata device canbe associated with range of vnis.struct vxlan_vni_node is introduced to representa configured vni. We start with vni and itsassociated remote_ip in this structure. Thisstructure can be extended to bring in otherper vni attributes if there are usecases for it.A vni inherits an attribute from the base vxlan deviceif there is no per vni attributes defined.struct vxlan_dev gets a new rhashtable forvnis called vxlan_vni_group. vxlan_vnifilter.cimplements the necessary netlink api, notificationsand helper functions to process and manage lifecycleof vxlan_vni_node.This patch also adds new helper functions in vxlan_multicast.cto handle per vni remote_ip multicast groups which are partof vxlan_vni_group.Fix build problems:Reported-by: kernel test robot Signed-off-by: Roopa Prabhu Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/vxlan/Makefile

a498c595 - vxlan_multicast: Move multicast helpers to a separate file

Tue, 01 Mar 2022 05:04:35 +0000

vxlan_multicast: Move multicast helpers to a separate filesubsequent patches will add more helpers.Signed-off-by: Roopa Prabhu Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/vxlan/Makefile

67653936 - vxlan: move to its own directory

Tue, 01 Mar 2022 05:04:28 +0000

vxlan: move to its own directoryvxlan.c has grown too long. This patch movesit to its own directory. subsequent patches add newfunctionality in new files.Signed-off-by: Roopa Prabhu Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/vxlan/Makefile