Recieved a verbal ack, so I applied this to master.
On 5 June 2014 09:26, Joe Stringer wrote:
> udpif->dump_seq already exists in master, and is changed by the leader
> revalidator thread.
>
>
> On 5 June 2014 06:29, Ethan Jackson wrote:
>
>> Maybe I'm missing something. But I'm not seeing whe
udpif->dump_seq already exists in master, and is changed by the leader
revalidator thread.
On 5 June 2014 06:29, Ethan Jackson wrote:
> Maybe I'm missing something. But I'm not seeing where the dump seq is
> incremented
>
>
> On Tuesday, June 3, 2014, Joe Stringer wrote:
>
>> Rather than setti
Maybe I'm missing something. But I'm not seeing where the dump seq is
incremented
On Tuesday, June 3, 2014, Joe Stringer wrote:
> Rather than setting and resetting the 'mark' field in the ukey, this
> patch introduces a seq to track whether a flow has been seen during the
> most recent dump. Thi
Rather than setting and resetting the 'mark' field in the ukey, this
patch introduces a seq to track whether a flow has been seen during the
most recent dump. This tidies the code and simplifies the logic for
detecting when flows are duplicated from the datapath.
Signed-off-by: Joe Stringer
---
v
