On Tue, Feb 3, 2015 at 3:18 PM, Jesse Gross <je...@nicira.com> wrote: > On Tue, Feb 3, 2015 at 2:33 PM, Thomas Graf <tg...@noironetworks.com> wrote: >> On 02/03/15 at 02:25pm, Pravin Shelar wrote: >>> I agree port will continue to accept non GBP frames but sets >>> TUNNEL_VXLAN_OPT which is odd. Since it is checking extension for the >>> vport. >>> Why not set TUNNEL_VXLAN_OPT according to received packet header/metadata? >> >> Good point. I will change it to set TUNNEL_VXLAN_OPT if enabled and >> metadata is actually provided. > > It seems like in general userspace should not allow different > extensions to share the same datapath port. This perhaps isn't much of > an issue right now but if you enable an extension on one VXLAN port > (on the userspace side) and have another that is vanilla then we > shouldn't silently use the extension for everything.
One other thought on this: Is it really right for the kernel to ignore unknown extensions? It seems like if the user has requested a particular mode and it just silently doesn't take effect because the kernel doesn't know about it that's not really great. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
