Re: [PATCH][net-next] bridge: increase mtu to 9000

2016-02-22 Thread Li RongQing
On Tue, Feb 23, 2016 at 1:58 AM, Stephen Hemminger wrote: >> guest VMs. >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399064 >> >> Signed-off-by: Li RongQing > > Your change works, but I agree with Hannes. Just allow up to 64 * 1024 like > loopback does. And no need for a #define f

Re: [PATCH][net-next] bridge: increase mtu to 9000

2016-02-22 Thread Stephen Hemminger
On Mon, 22 Feb 2016 17:29:11 +0800 roy.qing...@gmail.com wrote: > From: Li RongQing > > A linux bridge always adopts the smallest MTU of the enslaved devices. > When no device are enslaved, it defaults to a MTU of 1500 and refuses to > use a larger one. This is problematic when using bridges ens

Re: [PATCH][net-next] bridge: increase mtu to 9000

2016-02-22 Thread Rick Jones
On 02/22/2016 01:29 AM, roy.qing...@gmail.com wrote: From: Li RongQing A linux bridge always adopts the smallest MTU of the enslaved devices. When no device are enslaved, it defaults to a MTU of 1500 and refuses to use a larger one. This is problematic when using bridges enslaving only virtual

[PATCH][net-next] bridge: increase mtu to 9000

2016-02-22 Thread roy . qing . li
From: Li RongQing A linux bridge always adopts the smallest MTU of the enslaved devices. When no device are enslaved, it defaults to a MTU of 1500 and refuses to use a larger one. This is problematic when using bridges enslaving only virtual NICs (vnetX) like it's common with KVM guests. Steps t