Thx for the reminder, backported to branch-2.3,
On Thu, Dec 11, 2014 at 2:47 PM, Ben Pfaff wrote:
>
> Is this anything that needs backporting? (I don't know.)
>
> Thanks,
>
> Ben.
>
> On Fri, Dec 05, 2014 at 02:00:50PM -0800, Alex Wang wrote:
> > Thx for the review, applied to master,
> >
> > O
Is this anything that needs backporting? (I don't know.)
Thanks,
Ben.
On Fri, Dec 05, 2014 at 02:00:50PM -0800, Alex Wang wrote:
> Thx for the review, applied to master,
>
> On Fri, Dec 5, 2014 at 1:52 PM, Joe Stringer wrote:
>
> > On 4 December 2014 at 11:07, Alex Wang wrote:
> > > On curr
Thx for the review, applied to master,
On Fri, Dec 5, 2014 at 1:52 PM, Joe Stringer wrote:
> On 4 December 2014 at 11:07, Alex Wang wrote:
> > On current master, the 'struct tnl_port' in tunnel module will be
> > recreated whenever the global connectivity sequence number changes
> > (e.g. when
On 4 December 2014 at 11:07, Alex Wang wrote:
> On current master, the 'struct tnl_port' in tunnel module will be
> recreated whenever the global connectivity sequence number changes
> (e.g. when adding unrelated flow). This is unnecessary and could
> cause drop of tunnel packet if a lookup happe
On current master, the 'struct tnl_port' in tunnel module will be
recreated whenever the global connectivity sequence number changes
(e.g. when adding unrelated flow). This is unnecessary and could
cause drop of tunnel packet if a lookup happens between the removal
and recreate.
This commit fixes
