net/mlx5e: Consider geneve_opts for encap contexts

Browse source

Current algorithm for encap keys is legacy from initial vxlan
implementation and doesn't take into account all possible fields of a
tunnel. For example, for a Geneve tunnel, which may have additional TLV
options, they are ignored when comparing encap keys and a rule can be
attached to an incorrect encap entry.

Fix that by introducing encap_info_equal() operation in
struct mlx5e_tc_tunnel. Geneve tunnel type uses custom implementation,
which extends generic algorithm and considers options if they are set.

Fixes: 7f1a546e32 ("net/mlx5e: Consider tunnel type for encap contexts")
Signed-off-by: Dima Chumak <dchumak@nvidia.com>
Reviewed-by: Vlad Buslov <vladbu@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

...

This commit is contained in:

Dima Chumak 2021-02-11 09:36:33 +02:00 • committed by Saeed Mahameed

parent a7b76002ae

commit 929a2faddd

6 changed files with 51 additions and 14 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

10

drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun.h

View file

23

drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun_encap.c

View file

29

drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun_geneve.c

View file

1

drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun_gre.c

View file

1

drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun_mplsoudp.c

View file

1

drivers/net/ethernet/mellanox/mlx5/core/en/tc_tun_vxlan.c

View file