netdev - Re: [PATCH net v3 0/3] Set a large MTU on ovs-created tunnel devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 10 Feb 2016 05:50:46 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	david@...ve.works
Cc:	netdev@...r.kernel.org, dev@...nvswitch.org, jesse@...nel.org,
	hannes@...essinduktion.org, tgraf@...g.ch,
	roopa@...ulusnetworks.com, sergei.shtylyov@...entembedded.com
Subject: Re: [PATCH net v3 0/3] Set a large MTU on ovs-created tunnel
 devices

From: David Wragg <david@...ve.works>
Date: Wed, 10 Feb 2016 00:05:54 +0000

> Prior to 4.3, openvswitch tunnel vports (vxlan, gre and geneve) could
> transmit vxlan packets of any size, constrained only by the ability to
> send out the resulting packets.  4.3 introduced netdevs corresponding
> to tunnel vports.  These netdevs have an MTU, which limits the size of
> a packet that can be successfully encapsulated.  The default MTU
> values are low (1500 or less), which is awkwardly small in the context
> of physical networks supporting jumbo frames, and leads to a
> conspicuous change in behaviour for userspace.
> 
> This patch series sets the MTU on openvswitch-created netdevs to be
> the relevant maximum (i.e. the maximum IP packet size minus any
> relevant overhead), effectively restoring the behaviour prior to 4.3.
> 
> Where relevant, the limits on MTU values that can be directly set on
> the netdevs are also relaxed.
> 
> Changes in v2:
> * Extend to all openvswitch tunnel types, i.e. gre and geneve as well
> * Use IP_MAX_MTU
> 
> Changes in v3:
> * Fix block comment style

Series applied, thanks.