diff options
| author | Eric Dumazet <edumazet@google.com> | 2013-08-19 04:08:07 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2013-08-21 00:05:04 +0200 |
| commit | 734d2725db879f3f6fcdc2b1d2a5deae105f5e95 (patch) | |
| tree | 44648101fe8a2960add4c7d3b690f3fbcaac8841 /drivers/net/ethernet/myricom | |
| parent | vhost: Include linux/uio.h instead of linux/socket.h (diff) | |
| download | linux-734d2725db879f3f6fcdc2b1d2a5deae105f5e95.tar.xz linux-734d2725db879f3f6fcdc2b1d2a5deae105f5e95.zip | |
ipv4: raise IP_MAX_MTU to theoretical limit
As discussed last year [1], there is no compelling reason
to limit IPv4 MTU to 0xFFF0, while real limit is 0xFFFF
[1] : http://marc.info/?l=linux-netdev&m=135607247609434&w=2
Willem raised this issue again because some of our internal
regression tests broke after lo mtu being set to 65536.
IP_MTU reports 0xFFF0, and the test attempts to send a RAW datagram of
mtu + 1 bytes, expecting the send() to fail, but it does not.
Alexey raised interesting points about TCP MSS, that should be addressed
in follow-up patches in TCP stack if needed, as someone could also set
an odd mtu anyway.
Signed-off-by: Eric Dumazet <edumazet@google.com>
Cc: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Cc: Willem de Bruijn <willemb@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/ethernet/myricom')
0 files changed, 0 insertions, 0 deletions