[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150717105853.GB18033@pox.localdomain>
Date: Fri, 17 Jul 2015 12:58:53 +0200
From: Thomas Graf <tgraf@...g.ch>
To: Pravin Shelar <pshelar@...ira.com>
Cc: Simon Horman <simon.horman@...ronome.com>,
Roopa Prabhu <roopa@...ulusnetworks.com>, rshearma@...cade.com,
ebiederm <ebiederm@...ssion.com>,
Hannes Frederic Sowa <hannes@...essinduktion.org>,
Jesse Gross <jesse@...ira.com>,
David Miller <davem@...emloft.net>,
Daniel Borkmann <daniel@...earbox.net>, tom@...bertland.com,
Eric Dumazet <edumazet@...gle.com>,
Ji???? P??rko <jiri@...nulli.us>, marcelo.leitner@...il.com,
Stephen Hemminger <stephen@...workplumber.org>,
Justin Pettit <jpettit@...ira.com>,
Patrick McHardy <kaber@...sh.net>,
netdev <netdev@...r.kernel.org>,
"dev@...nvswitch.org" <dev@...nvswitch.org>
Subject: Re: [RFC net-next 22/22] openvswitch: Use regular GRE net_device
instead of vport
On 07/16/15 at 02:36pm, Pravin Shelar wrote:
> On Thu, Jul 16, 2015 at 7:52 AM, Thomas Graf <tgraf@...g.ch> wrote:
> > I'm inclined to change this and use an in-kernel API as well to
> > create the net_device just like VXLAN does in patch 21.
> >
> > Pravin, what do you think?
>
> About the vxlan APIs we also need to direct netlink interface for
> userspace to configure vxlan device. This will allow us to remove
> vxlan compat code from ovs vport-netdev.c in future.
Do you mean creating the tunnel devices from user space? This would
break existing users of the OVS Netlink interface. How do you want
to prevent that?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists