summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorSunil Rani <sunrani@nvidia.com>2021-03-10 01:53:39 +0300
committerSaeed Mahameed <saeedm@nvidia.com>2022-02-24 02:21:58 +0300
commit0b0ea3c5b1c087b20ee3edb8f0846bce5f08a807 (patch)
treed721c30ea11fcd303ab2e2bb190464053949262c /tools/perf/scripts/python/export-to-postgresql.py
parentc2c922dae77f36e24d246c6e310cee0c61afc6fb (diff)
downloadlinux-0b0ea3c5b1c087b20ee3edb8f0846bce5f08a807.tar.xz
net/mlx5: E-Switch, reserve and use same uplink metadata across ports
When in switchdev mode wire traffic will hit the FDB in one of two scenarios. - Shared FDB, in that case traffic from both physical ports should be tagged by the same metadata value so a single FDB rule could catch traffic from both ports. - Two E-Switches, traffic from each physical port will hit the native E-Switch which means traffic from one physical port can't reach the E-Switch of the other one. Looking at those two scenarios it means we can always use the same metadata value to tag wire traffic regardless of the mode. Reserve a single metadata value to be used to tag wire traffic. Signed-off-by: Sunil Rani <sunrani@nvidia.com> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions