ia64/xen-unstable

changeset 5006:47166e28f279

find changesets by author, revision, files, or words in the commit message
bitkeeper revision 1.1159.258.139 (428c9cbe7Sc87xp33OYAeObd7e3N3g)

Do not set jumbo MTU on the fake netfront/back loopback device. It
causes packet loss at the Ethernet bridge (since bridges do not
fragment IP packets).
Signed-off-by: Keir Fraser <keir@xensource.com>
author kaf24@firebug.cl.cam.ac.uk
date Thu May 19 14:03:42 2005 +0000 (2005-05-19)
parents 65f0179fc567
children 0c3e919d87f4 829173784dc1
files linux-2.6.11-xen-sparse/drivers/xen/netback/loopback.c
line diff
     1.1 --- a/linux-2.6.11-xen-sparse/drivers/xen/netback/loopback.c	Wed May 18 21:41:38 2005 +0000
     1.2 +++ b/linux-2.6.11-xen-sparse/drivers/xen/netback/loopback.c	Thu May 19 14:03:42 2005 +0000
     1.3 @@ -94,7 +94,15 @@ static void loopback_construct(struct ne
     1.4      dev->get_stats       = loopback_get_stats;
     1.5  
     1.6      dev->tx_queue_len    = 0;
     1.7 -    dev->mtu             = 16*1024;
     1.8 +
     1.9 +    /*
    1.10 +     * We do not set a jumbo MTU on the interface. Otherwise the network
    1.11 +     * stack will try to send large packets that will get dropped by the
    1.12 +     * Ethernet bridge (unless the physical Ethernet interface is configured
    1.13 +     * to transfer jumbo packets). If a larger MTU is desired then the system
    1.14 +     * administrator can specify it using the 'ifconfig' command.
    1.15 +     */
    1.16 +    /*dev->mtu             = 16*1024;*/
    1.17  }
    1.18  
    1.19  static int __init loopback_init(void)