[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200421133321.GD937199@lunn.ch>
Date: Tue, 21 Apr 2020 15:33:21 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Vladimir Oltean <olteanv@...il.com>
Cc: f.fainelli@...il.com, vivien.didelot@...il.com,
davem@...emloft.net, o.rempel@...gutronix.de,
netdev@...r.kernel.org
Subject: Re: [PATCH net 1/2] net: dsa: be compatible with DSA masters with
max_mtu of 1500 or less
On Tue, Apr 21, 2020 at 03:31:09PM +0300, Vladimir Oltean wrote:
> From: Vladimir Oltean <vladimir.oltean@....com>
>
> It would be ideal if the DSA switch ports would support an MTU of 1500
> bytes by default, same as any other net device. But there are 2 cases of
> issues with trying to do that:
>
> - Drivers that are legitimately MTU-challenged and don't support
> anything larger than ETH_DATA_LEN. A very quick search shows that
> sungem.c is one such example - there may be many others.
>
> - Drivers that simply don't populate netdev->max_mtu. In that case, it
> seems that the ether_setup function sets dev->max_mtu to a default
> value of ETH_DATA_LEN. And due to the above cases which really are
> MTU-challenged, we can't really make any guesses.
>
> So for these cases, if the max_mtu of the master net_device is lower
> than 1500, use that (minus the tagger overhead) as the max MTU of the
> switch ports.
I don't like this. I suspect this will also break in subtle ways.
Please go back to the original behaviour. Make the call to request the
minimum needed for DSA. And don't care at all if it fails. For jumbo
frames then you can error out.
Andrew
Powered by blists - more mailing lists