From: Thomas Falcon
Date: Thu, 26 Jan 2017 10:44:31 -0600
> On 01/25/2017 10:05 PM, David Miller wrote:
>> From: Thomas Falcon
>> Date: Wed, 25 Jan 2017 15:02:20 -0600
>>
>>> In the current driver, the MTU is set to the maximum value
>>> capable for the backing device. This patch sets the MTU to
On 01/25/2017 10:05 PM, David Miller wrote:
> From: Thomas Falcon
> Date: Wed, 25 Jan 2017 15:02:20 -0600
>
>> In the current driver, the MTU is set to the maximum value
>> capable for the backing device. This patch sets the MTU to the
>> default value for a Linux net device.
> Why are you doing t
From: Thomas Falcon
Date: Wed, 25 Jan 2017 15:02:20 -0600
> In the current driver, the MTU is set to the maximum value
> capable for the backing device. This patch sets the MTU to the
> default value for a Linux net device.
Why are you doing this?
What happens to users who depend upon the curre
In the current driver, the MTU is set to the maximum value
capable for the backing device. This patch sets the MTU to the
default value for a Linux net device. It also corrects a
discrepancy between MTU values received from firmware, which includes
the ethernet header length, and net device MTU val
