[PATCH net-next 00/22 v2] Lightweight & flow based encapsulation

2015-07-21 Thread Thomas Graf
This series combines the work previously posted by Roopa, Robert and myself. It's according to what we discussed at NFWS. The motivation of this series is to: * Consolidate code between OVS and the rest of the kernel and get rid of OVS vports and instead represent them as pure net_devices. *

Re: [PATCH net-next 00/22 v2] Lightweight & flow based encapsulation

2015-07-21 Thread David Miller
From: Thomas Graf Date: Tue, 21 Jul 2015 10:43:44 +0200 > This series combines the work previously posted by Roopa, Robert and > myself. It's according to what we discussed at NFWS. The motivation > of this series is to: > > * Consolidate code between OVS and the rest of the kernel and get >

Re: [ovs-dev] [PATCH net-next 00/22 v2] Lightweight & flow based encapsulation

2015-07-22 Thread thomas.morin
Hi Thomas, This looks promising. One question: will this approach allow MPLS-in-GRE and MPLS-in-UDP ? -Thomas 2015-07-21, Thomas Graf: This series combines the work previously posted by Roopa, Robert and myself. It's according to what we discussed at NFWS. The motivation of this series is to:

Re: [ovs-dev] [PATCH net-next 00/22 v2] Lightweight & flow based encapsulation

2015-07-22 Thread roopa
On 7/22/15, 1:58 AM, thomas.mo...@orange.com wrote: Hi Thomas, This looks promising. One question: will this approach allow MPLS-in-GRE and MPLS-in-UDP ? The current series was focused on IP to MPLS tunnels. But, the infrastructure allows associating encap state with routes and calling the r