nfp: flower: handle neighbour events on internal ports
authorJohn Hurley <john.hurley@netronome.com>
Wed, 28 Aug 2019 05:56:30 +0000 (22:56 -0700)
committerDavid S. Miller <davem@davemloft.net>
Wed, 28 Aug 2019 23:06:49 +0000 (16:06 -0700)
commite8024cb483abb2b0290b3ef5e34c736e9de2492f
tree952a02289d87f626e4976246543e75c65b77d85a
parent739d7c5752b255e89ddbb1b0474f3b88ef5cd343
nfp: flower: handle neighbour events on internal ports

Recent code changes to NFP allowed the offload of neighbour entries to FW
when the next hop device was an internal port. This allows for offload of
tunnel encap when the end-point IP address is applied to such a port.

Unfortunately, the neighbour event handler still rejects events that are
not associated with a repr dev and so the firmware neighbour table may get
out of sync for internal ports.

Fix this by allowing internal port neighbour events to be correctly
processed.

Fixes: 45756dfedab5 ("nfp: flower: allow tunnels to output to internal port")
Signed-off-by: John Hurley <john.hurley@netronome.com>
Reviewed-by: Simon Horman <simon.horman@netronome.com>
Reviewed-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
drivers/net/ethernet/netronome/nfp/flower/tunnel_conf.c