diff options
| author | Thomas Falcon <tlfalcon@linux.vnet.ibm.com> | 2017-02-14 19:22:59 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-02-14 22:57:45 +0300 |
| commit | f39f0d1e1e93145a0e91d9a7a639c42fd037ecc3 (patch) | |
| tree | c6f51606b311e9ee00235e9fc06301ff8fe23ba1 /net/packet | |
| parent | a60ced990e309666915d21445e95347d12406694 (diff) | |
| download | linux-f39f0d1e1e93145a0e91d9a7a639c42fd037ecc3.tar.xz | |
ibmvnic: Fix initial MTU settings
In the current driver, the MTU is set to the maximum value
capable for the backing device. This decision turned out to
be a mistake as it led to confusion among users. The expected
initial MTU value used for other IBM vNIC capable operating
systems is 1500, with the maximum value (9000) reserved for
when Jumbo frames are enabled. This patch sets the MTU to
the default value for a net device.
It also corrects a discrepancy between MTU values received from
firmware, which includes the ethernet header length, and net
device MTU values.
Finally, it removes redundant min/max MTU assignments after device
initialization.
Signed-off-by: Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/packet')
0 files changed, 0 insertions, 0 deletions