From: George Dunlap <george.dunlap@citrix.com>
To: Tim Deegan <Tim.Deegan@eu.citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Paul Durrant <Paul.Durrant@citrix.com>,
Keir Fraser <keir@xen.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
James Harper <james.harper@bendigoit.com.au>
Subject: Re: RFC: Doing a superpage zero-sweep on decrease_reservation
Date: Wed, 09 Mar 2011 15:00:06 +0000 [thread overview]
Message-ID: <1299682806.19262.4832.camel@elijah> (raw)
In-Reply-To: <20110309142335.GI28479@whitby.uk.xensource.com>
On Wed, 2011-03-09 at 14:23 +0000, Tim Deegan wrote:
> Do you think ballooned-out pages are likely to be in 2MB chunks of
> zeroed memory?
Sorry, didn't answer this. I think that for a large guest, the initial
balloon is very likely that for the first mfn freed in a superpage, that
mfn will turn out to have been in a 2MB chunks of zeroed memory, all of
which will eventually passed back to Xen anyway. (e.g., imagine a VM
with 32GiB static_max but a 16GiB target -- of the 16GiB of individual
4k pages passed back by the balloon driver, the vast majority of them
will be in a page which (1) is zeroed already and (2) will end up being
passed back entirely anyway.)
One could imagine the PV drivers allocating the full balloon size, then
going through and sorting the pages by pfn, consolidating the
superpages, and passing them back as one big chunk -- but that would be
a big waste of time compared to just having Xen optimistically reclaim
the whole superpage.
-George
prev parent reply other threads:[~2011-03-09 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 13:47 RFC: Doing a superpage zero-sweep on decrease_reservation George Dunlap
2011-03-09 14:23 ` Tim Deegan
2011-03-09 14:46 ` George Dunlap
2011-03-09 15:00 ` George Dunlap [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=1299682806.19262.4832.camel@elijah \
--to=george.dunlap@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=Tim.Deegan@eu.citrix.com \
--cc=james.harper@bendigoit.com.au \
--cc=keir@xen.org \
--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.