From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Keir Fraser <keir@xensource.com>
Cc: "Petersson, Mats" <Mats.Petersson@amd.com>,
xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: Re: [Xen-users] Re: Xen 3.1 released!
Date: Fri, 25 May 2007 15:56:25 +0200 [thread overview]
Message-ID: <4656EB09.2080409@wpkg.org> (raw)
In-Reply-To: <C27CA55D.F854%keir@xensource.com>
Keir Fraser schrieb:
> On 25/5/07 14:20, "Tomasz Chmielewski" <mangoo@wpkg.org> wrote:
>
>>> Hmmm... That's not so explicable. Obviously something in save/restore is
>>> causing unpageable allocations to happen. Could be pagetables for mappings
>>> of HVM guest memory, or something like that. Needs investigating further, I
>>> think.
>> Could be.
>>
>> Now that I repeated the save/restore a couple of times, total RAM usage
>> for dom0 jumps to ~700 MB sometimes during domain save (dom0 has now
>> about 2.3 GB RAM, domU has 1.7 GB RAM; 4 GB RAM installed now in the
>> machine).
>
> The only thing I would expect could so dramatically inflate dom0's memory
> usage would be caching of disc blocks from the saved image file. But we
> added explicit cache flushing to both domain-save and domain-restore before
> releasing 3.1. The flushes are only advisory though, so perhaps they are
> getting ignored for some reason.
For your notice, I just saw 1.3 GB RAM usage when doing a 1.7 GB HVM
domain save :)
--
Tomasz Chmielewski
http://wpkg.org
prev parent reply other threads:[~2007-05-25 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <907625E08839C4409CE5768403633E0B02561D3C@sefsexmb1.amd.com>
2007-05-25 10:54 ` [Xen-users] Re: Xen 3.1 released! Tomasz Chmielewski
2007-05-25 11:06 ` Petersson, Mats
2007-05-25 11:14 ` Tomasz Chmielewski
2007-05-25 11:58 ` Keir Fraser
2007-05-25 12:57 ` Tomasz Chmielewski
2007-05-25 13:05 ` Keir Fraser
2007-05-25 13:20 ` Tomasz Chmielewski
2007-05-25 13:38 ` Keir Fraser
2007-05-25 13:56 ` Tomasz Chmielewski [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=4656EB09.2080409@wpkg.org \
--to=mangoo@wpkg.org \
--cc=Mats.Petersson@amd.com \
--cc=keir@xensource.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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.