From: Patrick Scharrenberg <pittipatti@web.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Xen-devel@lists.xensource.com,
James Harper <james.harper@bendigoit.com.au>
Subject: Re: xen 3 dom0 eats memory - ME TOO
Date: Thu, 05 Jan 2006 13:26:34 +0100 [thread overview]
Message-ID: <43BD107A.7060100@web.de> (raw)
In-Reply-To: <669f61d0692c197d51c11b04bb9964c6@cl.cam.ac.uk>
Keir Fraser schrieb:
>> I'll add free memory to mrtg and see what that uncovers...
>
> Looks like somethign allocates lots of 64-byte buffers and never frees
> them. I don't currently know what is doing those allocations. It might
> be worth adding tracing to kmalloc().
I changed my configuration in the following way and now no memory gets
lost.
I leave the physical eth0 as it is when the machine boots, create a
bridge which holds all vif's of the domUs.
So I have no vif for dom0 and use the physical ethernet interface directly.
Turn on masquerading for eth0 like I did before.
Now it works.
It seems that the "virtualisazion" of the ethernet interface is
responsible for the troubles.
Patrick
prev parent reply other threads:[~2006-01-05 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 23:15 xen 3 dom0 eats memory - ME TOO James Harper
2006-01-05 10:27 ` Keir Fraser
2006-01-05 12:26 ` Patrick Scharrenberg [this message]
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=43BD107A.7060100@web.de \
--to=pittipatti@web.de \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=Xen-devel@lists.xensource.com \
--cc=james.harper@bendigoit.com.au \
/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.