All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Bruin <jmdebruin@xmsnet.nl>
To: xen-devel@lists.xensource.com
Subject: Limits on mtu size ?
Date: Fri, 07 Oct 2011 20:05:21 +0200	[thread overview]
Message-ID: <4E8F3F61.9070401@xmsnet.nl> (raw)

[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]


Network performance on fast physical networks usually increase by 
switching to larger packet sizes. So I decided to increase the mtu on my 
virtual networks to see if that has a positive effect. Anoyingly the 
bridge code does not allow you to increase the mtu above 1500 if no 
interface is attached to the bridge. Google tels me admins attach a nic 
to the bridge, increase the mtu and then remove the nic from the bridge 
as a work around. Then I noticed that the loopback has a whopping 16k 
mtu. For some reason adding lo to a bridge is not allowed. To shortcut 
workarounds and have fun with the mtu size I modified 
linux-2.6/net/bridge/br_if.c. There is a line: mtu = ETH_DATA_LEN; which 
I changed in to mtu = 16436; If lo can handle that size why not a 
bridge. So my setup now has two brides with oversized mtu's and one 
normal sized bidge to talk to my lan. This setup has run for two day's 
and now it suddenly broke while ssh/rsync-ing data between the to 
internal networks. A server called darkstar ran out of memory, as far as 
i can see with an empty swapfile, a server called orion, which was 
reseaving the data, stopped responding. Dom0 feels sluggish. So 16436 is 
to big and 9000 is not?

I have attached the complaints of darkstar. Its running out of kernel 
memory?

-- 
Hans

orion: 2 cpu, 1GB
darkstar: 2 cpu 512MB
...
dom0: 1 cpu's (dual core dual threaded), 1GB
kernels 3.1-rc7 and higher
xen 4.1.1
al pure pv.




[-- Attachment #2: log.bz2 --]
[-- Type: application/octet-stream, Size: 24557 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

             reply	other threads:[~2011-10-07 18:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07 18:05 Hans de Bruin [this message]
2011-10-07 22:29 ` Limits on mtu size ? James Harper
2011-10-08  6:39   ` Hans de Bruin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E8F3F61.9070401@xmsnet.nl \
    --to=jmdebruin@xmsnet.nl \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.