net/mlx5e: Support multiple encapsulations for a TC flow

Browse source

Currently a flow is associated with a single encap structure. The FW
extended destination features enables the driver to associate a flow
with multiple encap instances.

Change the encap id field from a flow scope to a per destination value
in the flow attributes struct. Use the encaps array to associate a flow
table entry with multiple encap entries.

Update the neigh logic to offload only if all encapsulations used in a
flow are connected, and un-offload upon the first one disconnected.

Note that the driver can now support up to two encap destinations.

Signed-off-by: Eli Britstein <elibr@mellanox.com>
Reviewed-by: Oz Shlomo <ozsh@mellanox.com>
Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>

...

This commit is contained in:

Eli Britstein 2018-11-18 14:21:46 +02:00 • committed by Saeed Mahameed

parent 79baaec719

commit 8c4dc42bf6

3 changed files with 62 additions and 33 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

85

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

View file

3

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

View file

7

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

View file