net/mlx5e: Use the full tunnel key info for encapsulation offload house-keeping

Browse source

Currently we use subset of the input tunnel key fields (id, ip daddr,
dst port) which are provided by upper layers to indentify flows that should
go through the same encapsulation and maintain the HW encapsulation table.

This is redundant and can get us wrong.

Instead, keep a copy of the ip tunnel info provided by the user
through TC and have the tunnel key part as the key to our internal hash.

Signed-off-by: Or Gerlitz <ogerlitz@mellanox.com>
Reviewed-by: Hadar Hen Zion <hadarh@mellanox.com>
Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>

...

This commit is contained in:

Or Gerlitz 2017-01-05 16:43:29 +02:00 • committed by Saeed Mahameed

parent 75c33da827

commit 76f7444dd5

2 changed files with 17 additions and 30 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

38

drivers/net/ethernet/mellanox/mlx5/core/en_tc.c

View file

9

drivers/net/ethernet/mellanox/mlx5/core/eswitch.h

View file