Is there an reason why this is limited to 1500 bytes? Could it be increased? Or, could the ioctl be implemented so it could be changed from the cmdline? It''d help with performance between dom0 and domU. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
xen-devel-bounces@lists.xensource.com wrote on 08/01/2005 06:58:23 PM:> Is there an reason why this is limited to 1500 bytes? Could it beincreased?> Or, could the ioctl be implemented so it could be changed from thecmdline?> It''d help with performance between dom0 and domU. >Usually Dom0 does MAC-level routing of packets for all domU''s using a bridge in dom0. Packets that go through the bridge don''t get fragmented, but go out the ethernet card directly. To make sure that all these packets have the default ethernet size they are limited to this MTU size. If you increase the MTU size, some connections might not work anymore. Stefan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, 2 Aug 2005, Stefan Berger wrote:> xen-devel-bounces@lists.xensource.com wrote on 08/01/2005 06:58:23 PM: > > > Is there an reason why this is limited to 1500 bytes? Could it be > increased? > > Or, could the ioctl be implemented so it could be changed from the > cmdline? > > It''d help with performance between dom0 and domU. > > > Usually Dom0 does MAC-level routing of packets for all domU''s using a > bridge in dom0. Packets that go through the bridge don''t get fragmented, > but go out the ethernet card directly. To make sure that all these packets > have the default ethernet size they are limited to this MTU size. If you > increase the MTU size, some connections might not work anymore.But we use routing. If a user is using bridging, and decides to change their MTU, let them. Other nodes on the physical lan may have also been altered. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel