[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aded81ea-2fca-4e5b-a3a1-011ec036b26b@genexis.eu>
Date: Fri, 16 Jan 2026 11:48:30 +0100
From: Benjamin Larsson <benjamin.larsson@...exis.eu>
To: Andrew Lunn <andrew@...n.ch>
Cc: Sayantan Nandy <sayantann11@...il.com>, lorenzo@...nel.org,
linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org,
netdev@...r.kernel.org, sayantan.nandy@...oha.com, bread.hsu@...oha.com,
kuldeep.malik@...oha.com, aniket.negi@...oha.com, rajeev.kumar@...oha.com
Subject: Re: [PATCH] net: airoha_eth: increase max mtu to 9220 for DSA jumbo
frames
Hi.
On 16/01/2026 02:08, Andrew Lunn wrote:
> On Thu, Jan 15, 2026 at 08:10:20PM +0100, Benjamin Larsson wrote:
>> On 15/01/2026 18:41, Andrew Lunn wrote:
>>> On Thu, Jan 15, 2026 at 02:18:37PM +0530, Sayantan Nandy wrote:
>>>> The Industry standard for jumbo frame MTU is 9216 bytes. When using DSA
>>>> sub-system, an extra 4 byte tag is added to each frame. To allow users
>>>> to set the standard 9216-byte MTU via ifconfig,increase AIROHA_MAX_MTU
>>>> to 9220 bytes (9216+4).
>>> What does the hardware actually support? Is 9220 the real limit? 10K?
>>> 16K?
>>>
>>> Andrew
>>>
>> Hi, datasheets say 16k and I have observed packet sizes close to that on the
>> previous SoC generation EN7523 on the tx path.
> Can you test 16K?
I probably can but it would take some time (weeks) as I dont have any
current setup with AN7581.
>
> Does it make any difference to the memory allocation? Some drivers
> allocate receive buffers based on the MAX MTU, not the current MTU, so
> can eat up a lot of memory which is unlikely to be used. We should try
> to avoid that.
>
> Thanks
> Andrew
Larger packets will consume more dma descriptors (a larger packet will
be split into several dma descriptors). So you dont allocate more memory
to be able to send jumbo frames.
MvH
Benjamin Larsson
Powered by blists - more mailing lists