aboutsummaryrefslogtreecommitdiffstats
path: root/include/uapi/linux/netconf.h
diff options
context:
space:
mode:
authorDaniel Borkmann <dborkman@redhat.com>2013-12-18 00:21:08 +0100
committerDavid S. Miller <davem@davemloft.net>2013-12-22 18:01:08 -0500
commit345010b5c488d754ecff98c4435a2a82949c9cf4 (patch)
tree74bc9c0f4cf20c54828271b2e2789820cf99dd4f /include/uapi/linux/netconf.h
parentnet: use kfree_skb_list() helper (diff)
downloadlinux-dev-345010b5c488d754ecff98c4435a2a82949c9cf4.tar.xz
linux-dev-345010b5c488d754ecff98c4435a2a82949c9cf4.zip
net: vxlan: use custom ndo_change_mtu handler
When adding a new vxlan device to an "underlying carrier" (here: dst->remote_ifindex), the MTU size assigned to the vxlan device is the MTU at setup time of the carrier - needed headroom, when adding a vxlan device w/o explicit carrier, then it defaults to 1500. In case of an explicit carrier that supports jumbo frames, we currently cannot change vxlan MTU via ip(8) to > 1500 in post-setup time, as vxlan driver uses eth_change_mtu() as default method for manually setting MTU. Hence, use a custom implementation that only falls back to eth_change_mtu() in case we didn't use a dev parameter on device setup time, and otherwise allow a max MTU setting of the carrier incl. adjustment for headroom. Reported-by: Shahed Shaikh <shahed.shaikh@qlogic.com> Signed-off-by: Daniel Borkmann <dborkman@redhat.com> Acked-by: Stephen Hemminger <stephen@networkplumber.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/uapi/linux/netconf.h')
0 files changed, 0 insertions, 0 deletions