diff options
| author | Roi Dayan <roid@nvidia.com> | 2021-08-04 02:19:53 +0300 |
|---|---|---|
| committer | Saeed Mahameed <saeedm@nvidia.com> | 2021-08-05 23:49:24 +0300 |
| commit | 2198b93279b2fa36bfc51c621d14f93244fb4965 (patch) | |
| tree | 69cf86dd820da6681aa12c2f8737b95a9bb3ab97 /include/linux | |
| parent | 5d5defd6b8915d031af5b71bf463991d14644f89 (diff) | |
| download | linux-2198b93279b2fa36bfc51c621d14f93244fb4965.tar.xz | |
net/mlx5e: Use shared mappings for restoring from metadata
FTEs are added with mapped metadata which is saved per eswitch.
When uplink reps are bonded and we are in a single FDB mode,
we could fail to find metadata which was stored on one eswitch mapping
but not the other or with a different id.
To resolve this issue use shared mapping between eswitch ports.
We do not have any conflict using a single mapping, for a type,
between the ports.
Signed-off-by: Roi Dayan <roid@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions