[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170613.173318.167061176274123943.davem@davemloft.net>
Date: Tue, 13 Jun 2017 17:33:18 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: magnus.damm@...il.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] via-rhine: add support for changing MTU
From: Magnus Damm <magnus.damm@...il.com>
Date: Wed, 14 Jun 2017 02:18:27 +0900
> From: Magnus Damm <damm+renesas@...nsource.se>
>
> Allow adjusting the MTU for via-rhine devices in case of no TX alignment
> buffer is used.
>
> Lightly tested on ALIX2D13 hardware by making use of VXLAN with MTU set
> to 1500 on top of via-rhine devices with 1550 MTU. Without this patch
> the VXLAN MTU is limited to less than 1500.
>
> Signed-off-by: Magnus Damm <damm+renesas@...nsource.se>
Why is the TX alignment buffer such an obstacle?
It would be so much nicer if this could be supported for all chip
variants instead of some certain subset which users have no idea
of figuring out. It's a really bad user experience to set them
up for failure like this.
Powered by blists - more mailing lists