Re: [ovs-dev] [net-next RFC 08/14] openvswitch: Allocate & attach ip_tunnel_info for tunnel set action

2015-06-03 Thread Thomas Graf
On 06/03/15 at 05:29pm, Jiri Benc wrote: > On Mon, 1 Jun 2015 16:27:32 +0200, Thomas Graf wrote: > > --- a/net/openvswitch/flow.h > > +++ b/net/openvswitch/flow.h > > @@ -45,6 +45,11 @@ struct sk_buff; > > #define TUN_METADATA_OPTS(flow_key, opt_len) \ > > ((void *)((flow_key)->tun_opts + TUN

Re: [ovs-dev] [net-next RFC 08/14] openvswitch: Allocate & attach ip_tunnel_info for tunnel set action

2015-06-03 Thread Jiri Benc
On Mon, 1 Jun 2015 16:27:32 +0200, Thomas Graf wrote: > --- a/net/openvswitch/flow.h > +++ b/net/openvswitch/flow.h > @@ -45,6 +45,11 @@ struct sk_buff; > #define TUN_METADATA_OPTS(flow_key, opt_len) \ > ((void *)((flow_key)->tun_opts + TUN_METADATA_OFFSET(opt_len))) > > +struct ovs_tunne

[ovs-dev] [net-next RFC 08/14] openvswitch: Allocate & attach ip_tunnel_info for tunnel set action

2015-06-01 Thread Thomas Graf
Make use of the new skb tunnel metadata field by allocating a ip_tunnel_info per OVS tunnel set action and then attaching that metadata to each skb that passes the set action. The old egress_tun_info via the OVS_CB() is left in place until all tunnel vports have been converted to the new method.