Re: [ovs-dev] [PATCH] tnl-neigh-cache: check for arp expiration.

2016-05-11 Thread pravin shelar
On Tue, May 10, 2016 at 3:40 PM, Joe Stringer wrote: > On 10 May 2016 at 10:37, pravin shelar wrote: >> On Fri, May 6, 2016 at 9:23 AM, Ben Pfaff wrote: >>> On Mon, Apr 25, 2016 at 03:58:33PM -0700, Pravin B Shelar wrote: The neighbor entry

Re: [ovs-dev] [PATCH] tnl-neigh-cache: check for arp expiration.

2016-05-10 Thread Joe Stringer
On 10 May 2016 at 10:37, pravin shelar wrote: > On Fri, May 6, 2016 at 9:23 AM, Ben Pfaff wrote: >> On Mon, Apr 25, 2016 at 03:58:33PM -0700, Pravin B Shelar wrote: >>> The neighbor entry expiry is only checked in dpif-poll >>> event handler, But in absence of any

Re: [ovs-dev] [PATCH] tnl-neigh-cache: check for arp expiration.

2016-05-10 Thread pravin shelar
On Fri, May 6, 2016 at 9:23 AM, Ben Pfaff wrote: > On Mon, Apr 25, 2016 at 03:58:33PM -0700, Pravin B Shelar wrote: >> The neighbor entry expiry is only checked in dpif-poll >> event handler, But in absence of any event we could keep >> using arp entry forever. This patch changes it

Re: [ovs-dev] [PATCH] tnl-neigh-cache: check for arp expiration.

2016-05-06 Thread Ben Pfaff
On Mon, Apr 25, 2016 at 03:58:33PM -0700, Pravin B Shelar wrote: > The neighbor entry expiry is only checked in dpif-poll > event handler, But in absence of any event we could keep > using arp entry forever. This patch changes it to check > expiration on each lookup. > > Signed-off-by: Pravin B

[ovs-dev] [PATCH] tnl-neigh-cache: check for arp expiration.

2016-04-25 Thread Pravin B Shelar
The neighbor entry expiry is only checked in dpif-poll event handler, But in absence of any event we could keep using arp entry forever. This patch changes it to check expiration on each lookup. Signed-off-by: Pravin B Shelar --- lib/tnl-neigh-cache.c | 10 +- 1 file