Re: [PATCH net-next v3 2/3] openvswitch: Use regular GRE net_device instead of vport

2015-08-04 Thread Alexei Starovoitov
On Tue, Aug 04, 2015 at 07:50:40PM -0700, Pravin Shelar wrote: > > I am planning on adding the ip_gre netlink interface later on. OVS > userspace needs same interface to directly create the GRE device > without vport-gre module. vport-gre module is compatibility code. If > you want I can do it in

Re: [PATCH net-next v3 2/3] openvswitch: Use regular GRE net_device instead of vport

2015-08-04 Thread Pravin Shelar
On Tue, Aug 4, 2015 at 7:27 PM, Alexei Starovoitov wrote: > On Tue, Aug 04, 2015 at 04:22:35PM -0700, Pravin B Shelar wrote: >> Following patch adds support for flow based tunnel to GRE >> tap deivces. Using flow based tunneling, we can implement >> OVS GRE vport. This patch removes all of the OVS

Re: [PATCH net-next v3 2/3] openvswitch: Use regular GRE net_device instead of vport

2015-08-04 Thread Alexei Starovoitov
On Tue, Aug 04, 2015 at 04:22:35PM -0700, Pravin B Shelar wrote: > Following patch adds support for flow based tunnel to GRE > tap deivces. Using flow based tunneling, we can implement > OVS GRE vport. This patch removes all of the OVS > specific GRE code and make OVS use a ip_gre net_device. > Min

[PATCH net-next v3 2/3] openvswitch: Use regular GRE net_device instead of vport

2015-08-04 Thread Pravin B Shelar
Following patch adds support for flow based tunnel to GRE tap deivces. Using flow based tunneling, we can implement OVS GRE vport. This patch removes all of the OVS specific GRE code and make OVS use a ip_gre net_device. Minimal GRE vport is kept to handle compatibility with current userspace appli