summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/Perf-Trace-Util/lib/Perf
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2024-06-15 05:30:41 +0300
committerJakub Kicinski <kuba@kernel.org>2024-06-15 05:30:41 +0300
commitabef84957b68994abfa4e0631b483f1bae732cbd (patch)
treed4d497acb6c950aee75f5a994601b7e3c3bff814 /tools/perf/scripts/python/Perf-Trace-Util/lib/Perf
parentafc5625e20971e8294a35b2f284a91b0601f9fce (diff)
parent4be3dcc9bf04d0957235b45ba18983f1f751a3a1 (diff)
downloadlinux-abef84957b68994abfa4e0631b483f1bae732cbd.tar.xz
Merge branch 'mlxsw-handle-mtu-values'
Petr Machata says: ==================== mlxsw: Handle MTU values Amit Cohen writes: The driver uses two values for maximum MTU, but neither is accurate. In addition, the value which is configured to hardware is not calculated correctly. Handle these issues and expose accurate values for minimum and maximum MTU per netdevice. Add test cases to check that the exposed values are really supported. Patch set overview: Patches #1-#3 set the driver to use accurate values for MTU Patch #4 aligns the driver to always use the same value for maximum MTU Patch #5 adds a test ==================== Link: https://lore.kernel.org/r/cover.1718275854.git.petrm@nvidia.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib/Perf')
0 files changed, 0 insertions, 0 deletions