summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2026-07-23 08:24:55 -0700
committerJakub Kicinski <kuba@kernel.org>2026-07-23 08:24:55 -0700
commit6bd1befbd3a8c0bb20e6fe9b48584861a4a0fed1 (patch)
treef67d8fc20d1e8abb5475049db7147c7b6e32cf98 /tools/perf/scripts/python
parentdef9a4745e105145133e442dd8a1c126caf0f553 (diff)
parent9173e1d3c7c7d49a71eee813091f9e834ec7cee5 (diff)
Merge branch 'net-mlx5e-report-zero-bandwidth-for-non-ets-traffic'
Tariq Toukan says: ==================== net/mlx5e: Report zero bandwidth for non-ETS traffic The IEEE 802.1Qaz standard restricts bandwidth allocation percentages to Enhanced Transmission Selection (ETS) traffic classes; STRICT, VENDOR, and CB Shaper TSA types carry no bandwidth semantics. Two problems exist in the mlx5e DCBNL ETS implementation: the get path reports 100% bandwidth for all TCs regardless of TSA type due to a hardware limitation, introduced by commit 820c2c5e773d ("net/mlx5e: Read ETS settings directly from firmware"), and the set path does not reject the unsupported CB Shaper TSA, introduced by commit 08fb1dacdd76 ("net/mlx5e: Support DCBNL IEEE ETS"). This series by Alexei Lazar fixes the get path to report zero bandwidth for non-ETS traffic classes, and rejects CB Shaper TSA configurations that the driver does not support. ==================== Link: https://patch.msgid.link/20260717075125.1244877-1-tariqt@nvidia.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions