[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <cover.1718275854.git.petrm@nvidia.com>
Date: Thu, 13 Jun 2024 16:07:53 +0200
From: Petr Machata <petrm@...dia.com>
To: "David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni
<pabeni@...hat.com>, <netdev@...r.kernel.org>
CC: Ido Schimmel <idosch@...dia.com>, Petr Machata <petrm@...dia.com>, "Amit
Cohen" <amcohen@...dia.com>, <mlxsw@...dia.com>
Subject: [PATCH net-next 0/5] 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
Amit Cohen (5):
mlxsw: port: Edit maximum MTU value
mlxsw: Adjust MTU value to hardware check
mlxsw: spectrum: Set more accurate values for netdevice min/max MTU
mlxsw: Use the same maximum MTU value throughout the driver
selftests: forwarding: Add test for minimum and maximum MTU
drivers/net/ethernet/mellanox/mlxsw/port.h | 3 +-
.../net/ethernet/mellanox/mlxsw/spectrum.c | 31 +-
.../net/ethernet/mellanox/mlxsw/spectrum.h | 1 -
.../mellanox/mlxsw/spectrum_buffers.c | 8 +-
.../testing/selftests/net/forwarding/Makefile | 1 +
.../selftests/net/forwarding/min_max_mtu.sh | 283 ++++++++++++++++++
6 files changed, 295 insertions(+), 32 deletions(-)
create mode 100755 tools/testing/selftests/net/forwarding/min_max_mtu.sh
--
2.45.0
Powered by blists - more mailing lists