From: David Ahern
Date: Wed, 12 Oct 2016 13:51:48 -0700
> The netdev adjacency tracking is failing to create proper dependencies
> for some topologies. For example this topology
>
> ++
> | myvrf |
> ++
> ||
> | +-+
>
On 10/13/16 1:34 AM, Jiri Pirko wrote:
>
> Although I didn't like the "all-list" idea when Veaceslav pushed it
> because it looked to me like a big hammer, it turned out to be very handy
> and quick for traversing neighbours. Why it cannot be fixed?
>
> The walks with possibly hundreds of functio
Wed, Oct 12, 2016 at 10:51:48PM CEST, d...@cumulusnetworks.com wrote:
>The netdev adjacency tracking is failing to create proper dependencies
>for some topologies. For example this topology
>
>++
>| myvrf |
>++
> ||
> | +-+
>
The netdev adjacency tracking is failing to create proper dependencies
for some topologies. For example this topology
++
| myvrf |
++
||
| +-+
| | macvlan |
| +-+
||
+---
