All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Scharrenberg <pittipatti@web.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Xen-devel@lists.xensource.com
Subject: Re: xen 3 dom0 eats memory
Date: Wed, 04 Jan 2006 15:47:45 +0100	[thread overview]
Message-ID: <43BBE011.4080709@web.de> (raw)
In-Reply-To: <bc370237d6b1b8ce436b262c28c4a91e@cl.cam.ac.uk>


>> I changed the setup in the following way:
>> - added an ip address to the bridge (in another subnet (B))
>> - changed domU ip address to a net B address
>> - added masquerading for eth0 in the postrouting-chain in dom0
>
> What iptables rules do you use to set this up?
I used "iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE" for 
masquerading.

> Is the gateway address for domU the net B address interface you add to 
> the bridge?
Yes that right, i forgot to mention that.

I have one official address on dom0 eth0 and a privat class B network 
for the domU's.
The address used on the bridge is from this private network and the 
gateway for the domU's

> It's worth trying 'ethtool -K eth0 tx off' in domU to turn off 
> checksum offload, just in case that is causing problems.
Checksum offload is turned off in all domU's.

The problem only appears if the pakets are masqueraded. Pinging the 
gateway-address (the one on the bridge-if) or the dom0-eth0-address 
causes no memory consumption

Patrick

  reply	other threads:[~2006-01-04 14:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04 13:43 xen 3 dom0 eats memory Patrick Scharrenberg
2006-01-04 14:35 ` Keir Fraser
2006-01-04 14:47   ` Patrick Scharrenberg [this message]
2006-01-04 14:58     ` Keir Fraser
2006-01-04 15:35       ` Patrick Scharrenberg
2006-01-04 15:52         ` Keir Fraser
2006-01-04 16:39           ` Patrick Scharrenberg
2006-01-04 16:52             ` Keir Fraser
2006-01-06 11:17               ` Patrick Scharrenberg
  -- strict thread matches above, loose matches on Subject: below --
2006-01-04 14:34 Ian Pratt
2006-01-04 16:22 ` Patrick Scharrenberg
2006-01-04 16:43   ` Keir Fraser

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=43BBE011.4080709@web.de \
    --to=pittipatti@web.de \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --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.