On Feb 14, 2013, at 8:37 AM, Kyle Mestery <kmest...@cisco.com>
wrote:
> With the recent flow based tunneling changes, VXLAN support was broken. These
> patches address this by enabling VXLAN to work as it did before flow based
> tunneling was pushed upstream.
>
> Kyle Mestery (6):
> Modify netdev_vport_get_dpif_port() to return a name for VXLAN ports
> which includes the destination UDP port number as a part of the
> name.
> Modify dpif_linux_port_add() to set the destination port for VXLAN
> ports.
> Add utility functions to the simap structure. These are used by future
> patches in this seris. The functions added are.
> Move dpif_backer->tnl_backers from a "struct sset" to a "struct
> simap". Store odp_port in the new map. This will make it easier
> to access the odp_port for future patches.
> In tnl_set_config(), when determining if a tunnel port already exists,
> make sure to also check the destination port. For VXLAN, this
> can be different and allows multiple VXLAN ports in the datapath
> to be created.
> Garbage collect tnl_backers during type_run(). Add new tnl_backers if
> a VXLAN ports UDP port changes.
>
> datapath/tunnel.c | 18 ++++++-
> lib/dpif-linux.c | 11 ++++
I should note, these patches enable basic VXLAN support with flow
based tunneling. Thanks to Ethan for helping with these, I appreciate
his guidance! I'm still chasing a few other things down, but these
patches are stable now.
Things left to do:
1) Add unit tests for VXLAN.
2) Figure out why when using multiple VXLAN ports traffic stops.
3) Changing a dst_port causes traffic in the data path over a VXLAN
port to stop.
I'm looking at these now and will send new patches once I address them.
Thanks,
Kyle
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
