From: Sandeep Haemoon <sandeeph@loljews.com>
To: netdev@vger.kernel.org
Cc: Felix Fietkau <nbd@nbd.name>,
Lorenzo Bianconi <lorenzo@kernel.org>,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/2] net: ethernet: mtk_eth_soc: 9K jumbo frame support
Date: Mon, 2 Nov 2026 00:58:23 +0200 [thread overview]
Message-ID: <patch-4f863a941889f0bceca1c082f2d79624@loljews.com> (raw)
This series makes the MediaTek SoC ethernet driver support 9K jumbo
frames on the 10G XGMII MACs (MT7988). The driver currently advertises
a 2030-byte max_mtu and programs the MAC max-rx field for at most 2048
bytes, so MTU > 2K is rejected and 9K frames are not usable.
Patch 1 adds the MTK_NETSYS_RX_9K capability, advertises 9K max_mtu on
the XGMII MACs (from the DT phy_mode at probe, so DSA can raise the
conduit MTU before the netdev is opened), programs XMAC_RX_CFG2,
derives the shared RX buffer length from the largest MTU, sizes the RX
rings from it, and programs the PDMA RX SDL max frame. A runtime MTU
change that would need a different ring buffer size is rejected with
-EBUSY while DMA is running; the rings are sized at the next open.
Patch 2 stops creating a page_pool for RX rings whose buffers do not
fit in an order-0 page (jumbo and HW-LRO rings). page_pool is created
with MTK_PP_MAX_BUF_SIZE and order 0; using it for 9K buffers would
overrun. The large-buffer path already uses mtk_max_buf_alloc().
This work is a forward-port of the MediaTek downstream jumbo series:
Mason Chang's "change default rx buffer length", "add 9k jumbo frame
support" and "add dynamic rx buffer adjustment support" (MediaTek
OpenWrt feed 999-eth-30/31/33, carried in
frank-w/BPI-Router-Linux), plus Frank Wunderlich's "try to fix crash
the right way". The per-ring page_pool rule is added here to make the
9K path safe without disabling page_pool for every ring.
The equivalent change was tested on a BPI-R4 Pro 8X (MT7988, 10G lan6 /
MxL86252) on the 6.18.60 backport: with both ends at MTU 9000, 8K ICMP
passes and iperf3 with MSS 8900 reaches ~9.87 Gbit/s (vs ~2.57 Gbit/s
at MSS 1460); the DSA conduit is raised to 9004 at boot. This v7.3
series is compile-tested with CONFIG_NET_MEDIATEK_SOC=y and
COMPILE_TEST=y; no hardware run of this exact tree yet.
The runtime-reallocation patch is not included: it reallocates the
shared RX rings when the MTU changes while an interface is up, removing
the -EBUSY restriction. It is a larger change and will be sent
separately.
Sandeep Haemoon (2):
net: ethernet: mtk_eth_soc: add 9K jumbo frame support
net: ethernet: mtk_eth_soc: skip page_pool for large RX buffers
drivers/net/ethernet/mediatek/mtk_eth_soc.c | 142 ++++++++++++++++----
drivers/net/ethernet/mediatek/mtk_eth_soc.h | 9 +-
2 files changed, 122 insertions(+), 29 deletions(-)
base-commit: c03c1a14507dfaf8b856c2608f9ac216021fc222
--
2.53.0
next reply other threads:[~2026-11-01 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 22:58 Sandeep Haemoon [this message]
2026-11-01 22:48 ` [PATCH net-next 1/2] net: ethernet: mtk_eth_soc: add 9K jumbo frame Sandeep Haemoon
2026-11-01 22:48 ` [PATCH net-next 2/2] net: ethernet: mtk_eth_soc: skip page_pool for Sandeep Haemoon
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=patch-4f863a941889f0bceca1c082f2d79624@loljews.com \
--to=sandeeph@loljews.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lorenzo@kernel.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
/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
all inboxes | Powered by JetHome®