Paul Blakey 5dbe906ff1 net/mlx5e: Use a slow path rule instead if vxlan neighbour isn't available ... When adding a vxlan tc rule, and a neighbour isn't available, we don't insert any rule to hardware. Once we enable offloading flows with multiple priorities, a packet that should have matched this rule will continue in hardware pipeline and might match a wrong one. This is unlike in tc software path where it will be matched and forwarded to the vxlan device (which will cause a ARP lookup eventually) and stop processing further tc filters. To address that, when when a neighbour isn't available (EAGAIN from attach_encap), or gets deleted, change the original action to be a forward to slow path instead. Neighbour update will restore the original action once the neighbour becomes available. This will be done atomically so at any given time we will have a the correct match. Signed-off-by: Paul Blakey <paulb@mellanox.com> Reviewed-by: Or Gerlitz <ogerlitz@mellanox.com> Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>		2018-10-17 14:20:49 -07:00
..
mlx4	Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net	2018-10-12 21:38:46 -07:00
mlx5/core	net/mlx5e: Use a slow path rule instead if vxlan neighbour isn't available	2018-10-17 14:20:49 -07:00
mlxfw
mlxsw	mlxsw: spectrum: Add NVE packet traps	2018-10-11 10:08:23 -07:00
Kconfig
Makefile