[ovs-dev] [RFC PATCH] datapath: allow tunnels to be created with rtnetlink

[Pravin Shelar]

On Wed, Dec 7, 2016 at 12:37 AM, Jiri Benc <jbenc at redhat.com> wrote:
> On Wed, 7 Dec 2016 09:03:39 +0800, Yang, Yi wrote:
>> But ovs userspace use genetlink to create vxlan tunnel port when we
>> build ovs to use its own compat modules, this is case 3 Pravin, how
>> do you think we can handle this?
>
> Where's the problem? I don't see any.
>
>> Now the dilemma is we can't create vxlangpe port although it has been
>> in ovs, I know it is ok if we use upstream tunnel code, but in many
>> cases, Linux distribution didn't include recent kernels, we have to
>> use ovs' compat modules, Pravin's comments also addressed this.
>
> There's no problem in using VXLAN-GPE in the out of tree driver using
> rtnetlink. As Eric wrote, we're working on this.
>

In compat mode, OVS tunnel devices are not used in same way as LWT,
since OVS do support kernel version that does not have core LWT
support. Therefore we have to use legacy vport APIs to create these
ports. There might be a way to configure the device, once it is
created, using rtnetlink API but would complicate the code. So I think
in such cases like GPE we could to add code to the legacy code.