[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180704203556.GC23469@lunn.ch>
Date: Wed, 4 Jul 2018 22:35:56 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: netdev@...r.kernel.org, "David S . Miller" <davem@...emloft.net>,
Michał Mirosław <mirq-linux@...e.qmqm.pl>,
Florian Fainelli <f.fainelli@...il.com>,
Paulius Zaleckas <paulius.zaleckas@...il.com>,
Hans Ulli Kroll <ulli.kroll@...glemail.com>,
Janos Laube <janos.dev@...il.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH net-next 5/5 v2] net: gemini: Indicate that we can handle
jumboframes
On Wed, Jul 04, 2018 at 08:33:24PM +0200, Linus Walleij wrote:
> The hardware supposedly handles frames up to 10236 bytes and
> implements .ndo_change_mtu() so accept 10236 minus the ethernet
> header for a VLAN tagged frame on the netdevices. Use
> ETH_MIN_MTU as minimum MTU.
>
> Signed-off-by: Linus Walleij <linus.walleij@...aro.org>
Hi Linus
Did you try with an MTU of 68? Maybe the vendor picked 256 because of
a hardware limit?
Otherwise the change looks good.
Andrew
Powered by blists - more mailing lists