openvswitch: Use regular VXLAN net_device device
This gets rid of all OVS specific VXLAN code in the receive and transmit path by using a VXLAN net_device to represent the vport. Only a small shim layer remains which takes care of handling the VXLAN specific OVS Netlink configuration. Unexports vxlan_sock_add(), vxlan_sock_release(), vxlan_xmit_skb() since they are no longer needed. Signed-off-by:Thomas Graf <tgraf@suug.ch> Signed-off-by:
Pravin B Shelar <pshelar@nicira.com> Signed-off-by:
David S. Miller <davem@davemloft.net>
Showing
- drivers/net/vxlan.c 116 additions, 126 deletionsdrivers/net/vxlan.c
- include/net/rtnetlink.h 1 addition, 0 deletionsinclude/net/rtnetlink.h
- include/net/vxlan.h 4 additions, 20 deletionsinclude/net/vxlan.h
- net/core/rtnetlink.c 17 additions, 9 deletionsnet/core/rtnetlink.c
- net/openvswitch/Kconfig 0 additions, 12 deletionsnet/openvswitch/Kconfig
- net/openvswitch/Makefile 0 additions, 1 deletionnet/openvswitch/Makefile
- net/openvswitch/flow_netlink.c 3 additions, 3 deletionsnet/openvswitch/flow_netlink.c
- net/openvswitch/vport-netdev.c 198 additions, 3 deletionsnet/openvswitch/vport-netdev.c
- net/openvswitch/vport-vxlan.c 0 additions, 322 deletionsnet/openvswitch/vport-vxlan.c
- net/openvswitch/vport-vxlan.h 0 additions, 11 deletionsnet/openvswitch/vport-vxlan.h
Please register or sign in to comment