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

Jiri Benc jbenc at redhat.com
Wed Dec 7 08:37:30 UTC 2016


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.

> So anybody will change current genetlink in ovs to rtnetlink? I will
> try to change it if nobody will fix it. Another issue, I think ovs
> will send rtnetlink message to kernel, right? Can ovs handle
> rtnetlink message if we use ovs compat modules instead of upstream
> kernel modules?

I don't see any problem.

We know how to handle all of the cases. Eric took over the work from
Thadeu and he has been working on the patches. Nobody prevents you from
submitting your own patches; but please do your own research in such
case first. By asking tons of question you're not speeding things up,
as we'll be spending time explaining instead of writing and testing the
code.

 Jiri


More information about the dev mailing list