summaryrefslogtreecommitdiffstats
path: root/certs
diff options
context:
space:
mode:
authorGavi Teitz <gavi@mellanox.com>2019-05-23 09:58:56 +0300
committerSaeed Mahameed <saeedm@mellanox.com>2019-06-28 16:04:00 -0700
commita90f88fe557d7f2318b724a93875dcaac45b5f05 (patch)
treeaf0693779b5553b720a40969d172360fb6d64cff /certs
parent5233794b179136d597b84188c1285148f07012e6 (diff)
downloadlinux-a90f88fe557d7f2318b724a93875dcaac45b5f05.tar.bz2
net/mlx5e: Don't refresh TIRs when updating representor SQs
Refreshing TIRs is done in order to update the TIRs with the current state of SQs in the transport domain, so that the TIRs can filter out undesired self-loopback packets based on the source SQ of the packet. Representor TIRs will only receive packets that originate from their associated vport, due to dedicated steering, and therefore will never receive self-loopback packets, whose source vport will be the vport of the E-Switch manager, and therefore not the vport associated with the representor. As such, it is not necessary to refresh the representors' TIRs, since self-loopback packets can't reach them. Since representors only exist in switchdev mode, and there is no scenario in which a representor will exist in the transport domain alongside a non-representor, it is not necessary to refresh the transport domain's TIRs upon changing the state of a representor's queues. Therefore, do not refresh TIRs upon such a change. Achieve this by adding an update_rx callback to the mlx5e_profile, which refreshes TIRs for non-representors and does nothing for representors, and replace instances of mlx5e_refresh_tirs() upon changing the state of the queues with update_rx(). Signed-off-by: Gavi Teitz <gavi@mellanox.com> Reviewed-by: Roi Dayan <roid@mellanox.com> Reviewed-by: Tariq Toukan <tariqt@mellanox.com> Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>
Diffstat (limited to 'certs')
0 files changed, 0 insertions, 0 deletions