[ovs-dev] [PATCH v2 1/3] ofproto-dpif-sflow: propagate actions within clone

2017-12-14 Thread Zoltan Balogh
By avoiding Tx recirculation and embracing tnl_push action within clone, the tunnel metadata is not propagated. Unless clone action is handled in the dpif_sflow_read_actions() function as well. This commit resolves this issue. In addition, some sflow data needs to be stored and restored in ofproto-

Re: [ovs-dev] [PATCH v2 1/3] ofproto-dpif-sflow: propagate actions within clone

2018-01-04 Thread Ben Pfaff
On Thu, Dec 14, 2017 at 09:56:19AM +0100, Zoltan Balogh wrote: > By avoiding Tx recirculation and embracing tnl_push action within clone, > the tunnel metadata is not propagated. Unless clone action is handled in > the dpif_sflow_read_actions() function as well. This commit resolves > this issue. >

Re: [ovs-dev] [PATCH v2 1/3] ofproto-dpif-sflow: propagate actions within clone

2018-01-05 Thread Zoltán Balogh
> On Thu, Dec 14, 2017 at 09:56:19AM +0100, Zoltan Balogh wrote: > > By avoiding Tx recirculation and embracing tnl_push action within clone, > > the tunnel metadata is not propagated. Unless clone action is handled in > > the dpif_sflow_read_actions() function as well. This commit resolves > > thi