diff options
| author | Or Har-Toov <ohartoov@nvidia.com> | 2026-10-04 11:35:31 +0300 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-10-06 18:03:00 -0700 |
| commit | 86b785b18f8f4a6b4a7392d1e2b29d6bb095011a (patch) | |
| tree | 492464e2360618bdba7e16e25c67efbcf03a8e31 /tools/perf/scripts/python/task-analyzer.py | |
| parent | 6fa2e7db99fb9ed67496c652fcfce5a31c6b73d0 (diff) | |
| download | linux-86b785b18f8f4a6b4a7392d1e2b29d6bb095011a.tar.gz linux-86b785b18f8f4a6b4a7392d1e2b29d6bb095011a.zip | |
Revert "net/mlx5: E-Switch, preserve max tx speed on vport state modification"
This reverts commit ad0ae7aefa7a ("net/mlx5: E-Switch, preserve max tx
speed on vport state modification").
mlx5_modify_vport_admin_state() and mlx5_esw_adj_vport_modify() query
the vport's current max_tx_speed before modifying its state, and
write that value back, to avoid resetting it to 0 as a side effect
of an unrelated admin-state change.
That's unnecessary: max_tx_speed is optional in MODIFY_VPORT_STATE -
FW skips writing it whenever it's 0, treating that as "not provided"
rather than "reset to zero". Leaving it unset already preserves FW's
current value, with no query needed.
Fixes: ad0ae7aefa7a ("net/mlx5: E-Switch, preserve max tx speed on vport state modification")
Signed-off-by: Or Har-Toov <ohartoov@nvidia.com>
Reviewed-by: Mark Bloch <mbloch@nvidia.com>
Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
Link: https://patch.msgid.link/20261004083531.216988-1-tariqt@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions
