lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f0683837-73cd-4478-9f00-044875a0da75@lunn.ch>
Date: Fri, 16 Jan 2026 15:21:04 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Benjamin Larsson <benjamin.larsson@...exis.eu>
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

On Fri, Jan 16, 2026 at 11:48:30AM +0100, Benjamin Larsson wrote:
> 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.

So it 'costs' nothing to declare the actual maximum.

For the moment, 9220 seems acceptable, but please include in the
commit message that the real maximum is higher, probably somewhere
around 16K.

	Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ