This is a minor issue but visible e.g. when you try to flush the neigh
cache while the ARP flow is still present in the datapath, triggering
the revalidation of the datapath flows which subsequently
refreshes/adds the entry in the cache.
Signed-off-by: Paolo Valerio
---
v2:
- renamed update -> al
Gaëtan Rivet writes:
> On Tue, Nov 2, 2021, at 18:12, Paolo Valerio wrote:
>> This is a minor issue but visible e.g. when you try to flush the neigh
>> cache while the ARP flow is still present in the datapath, triggering
>> the revalidation of the datapath flows which subsequently
>> refreshes/a
On Tue, Nov 2, 2021, at 18:12, Paolo Valerio wrote:
> This is a minor issue but visible e.g. when you try to flush the neigh
> cache while the ARP flow is still present in the datapath, triggering
> the revalidation of the datapath flows which subsequently
> refreshes/adds the entry in the cache.
>
This is a minor issue but visible e.g. when you try to flush the neigh
cache while the ARP flow is still present in the datapath, triggering
the revalidation of the datapath flows which subsequently
refreshes/adds the entry in the cache.
Signed-off-by: Paolo Valerio
---
lib/tnl-neigh-cache.c
