netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Machata <petrm@nvidia.com>
To: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	<netdev@vger.kernel.org>
Cc: Ido Schimmel <idosch@nvidia.com>, Petr Machata <petrm@nvidia.com>,
	"Amit Cohen" <amcohen@nvidia.com>, <mlxsw@nvidia.com>
Subject: [PATCH net-next 0/5] mlxsw: Handle MTU values
Date: Thu, 13 Jun 2024 16:07:53 +0200	[thread overview]
Message-ID: <cover.1718275854.git.petrm@nvidia.com> (raw)

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


             reply	other threads:[~2024-06-13 14:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 14:07 Petr Machata [this message]
2024-06-13 14:07 ` [PATCH net-next 1/5] mlxsw: port: Edit maximum MTU value Petr Machata
2024-06-13 14:07 ` [PATCH net-next 2/5] mlxsw: Adjust MTU value to hardware check Petr Machata
2024-06-13 14:07 ` [PATCH net-next 3/5] mlxsw: spectrum: Set more accurate values for netdevice min/max MTU Petr Machata
2024-06-13 14:07 ` [PATCH net-next 4/5] mlxsw: Use the same maximum MTU value throughout the driver Petr Machata
2024-06-13 14:07 ` [PATCH net-next 5/5] selftests: forwarding: Add test for minimum and maximum MTU Petr Machata
2024-06-15  2:40 ` [PATCH net-next 0/5] mlxsw: Handle MTU values patchwork-bot+netdevbpf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1718275854.git.petrm@nvidia.com \
    --to=petrm@nvidia.com \
    --cc=amcohen@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=mlxsw@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).