From: patchwork-bot+netdevbpf@kernel•org
To: Sayantan Nandy <sayantann11@gmail•com>
Cc: lorenzo@kernel•org, linux-arm-kernel@lists•infradead.org,
linux-mediatek@lists•infradead.org, netdev@vger•kernel.org,
sayantan.nandy@airoha•com, bread.hsu@airoha•com,
kuldeep.malik@airoha•com, aniket.negi@airoha•com,
brown.huang@airoha•com
Subject: Re: [PATCH net-next v3] net: airoha_eth: increase max MTU to 9220 for DSA jumbo frames
Date: Wed, 21 Jan 2026 02:40:44 +0000 [thread overview]
Message-ID: <176896324459.699622.2094070103891917067.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260119073658.6216-1-sayantann11@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Mon, 19 Jan 2026 13:06:58 +0530 you wrote:
> The industry standard jumbo frame MTU is 9216 bytes. When using the DSA
> subsystem, a 4-byte tag is added to each Ethernet frame.
>
> Increase AIROHA_MAX_MTU to 9220 bytes (9216 + 4) so that users can set a
> standard 9216-byte MTU on DSA ports.
>
> The underlying hardware supports significantly larger frame sizes
> (approximately 16K). However, the maximum MTU is limited to 9220 bytes
> for now, as this is sufficient to support standard jumbo frames and does
> not incur additional memory allocation overhead.
>
> [...]
Here is the summary with links:
- [net-next,v3] net: airoha_eth: increase max MTU to 9220 for DSA jumbo frames
https://git.kernel.org/netdev/net-next/c/6406fc709ace
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-21 2:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 7:36 [PATCH net-next v3] net: airoha_eth: increase max MTU to 9220 for DSA jumbo frames Sayantan Nandy
2026-01-19 14:50 ` Andrew Lunn
2026-01-19 16:14 ` Lorenzo Bianconi
2026-01-21 2:40 ` patchwork-bot+netdevbpf [this message]
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=176896324459.699622.2094070103891917067.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=aniket.negi@airoha$(echo .)com \
--cc=bread.hsu@airoha$(echo .)com \
--cc=brown.huang@airoha$(echo .)com \
--cc=kuldeep.malik@airoha$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-mediatek@lists$(echo .)infradead.org \
--cc=lorenzo@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sayantan.nandy@airoha$(echo .)com \
--cc=sayantann11@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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