From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [PATCH] set mtu from bridge also on vif interface Date: Mon, 7 Feb 2011 10:25:24 +0100 Message-ID: <20110207092524.GA25787@aepfle.de> References: <20110206134123.GA9752@aepfle.de> <1297069638.13091.727.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <1297069638.13091.727.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Mon, Feb 07, Ian Campbell wrote: > On Sun, 2011-02-06 at 13:41 +0000, Olaf Hering wrote: > > Apply mtu size from bridge interface also in vif interface. > > This depends on a kernel change which allows arbitrary mtu sizes until > > the frontend driver has connected to the backend driver. Without this > > kernel change, the vif mtu size will be limited to 1500 even with this > > change to the vif-bridge script. > > > > Signed-off-by: Olaf Hering > > In my experience the bridge will only allow it's MTU to be set to the > minimum of all the ports (or 1500ish if there are no ports) and will > reset to the new minimum when you add a new port. > > So does this patch do anything in the absence of the ability to > configure the MTU of a VIF from the toolstack? This depends if the bridge interface is part of the Xen toolstack configuration or if the bridge is part of the system configuration. In my setup the bridge is part of the system configuration and gets its mtu from the config of the physical interface, eth0 in my case. So br0 has mtu of 9000 already when vif-bridge runs. With this change, the vif interfaces follow the system configuration. Olaf