net/mlx5: introduce encapsulation rules container
authorViacheslav Ovsiienko <viacheslavo@mellanox.com>
Sat, 29 Dec 2018 19:55:37 +0000 (19:55 +0000)
committerFerruh Yigit <ferruh.yigit@intel.com>
Mon, 14 Jan 2019 16:44:30 +0000 (17:44 +0100)
commit18c3e6c90b5bc590a71d328d2b3e41df256cbb0c
tree65776bf89fd2ebcd4a1faa8002620e65e270b39c
parent4b837fe90e3d1e5980b39a7989134a9a16904390
net/mlx5: introduce encapsulation rules container

Currently the VXLAN encapsulation neigh/local rules
are stored in the list contained in the VTEP device
structure. Encapsulation VTEP device is attached to
outer interface and stored rules are related to this
underlying interface. We are going to use unattached
VXLAN devices for encapsulation (kernel does not use
attached interface to find egress one), so we should
introduce the structure to keep interface related
neigh/local rules instead of VTEP structure. This
patch introduces internal tcf_irule structure, and
its create/delete methods.

Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Acked-by: Shahaf Shuler <shahafs@mellanox.com>
drivers/net/mlx5/mlx5_flow_tcf.c