xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <George.Dunlap@eu.citrix.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: Tim Deegan <Tim.Deegan@eu.citrix.com>,
	Paul Durrant <Paul.Durrant@citrix.com>,
	xen devel <xen-devel@lists.xensource.com>
Subject: Re: what happens when a PoD page is touched?
Date: Mon, 16 May 2011 11:05:20 +0100	[thread overview]
Message-ID: <BANLkTimG+HK=dWm-w9M6LirhFxaiWy532A@mail.gmail.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01D570EB@trantor>

On Mon, May 16, 2011 at 10:22 AM, James Harper
<james.harper@bendigoit.com.au> wrote:
> I've not seen any slowdown on boot with any version of Windows until I
> go to actually do the balloon down...

You mean, you don't see slowness on boot unless you boot with maxmem
!= memory (i.e,. in PoD mode)?

For one thing, after the balloon driver is finished with its initial
allocation, there shouldn't be any sweeping; if there is, then it may
be that you're not actually inflating the balloon as much as Xen
thinks you should.

Before the balloon driver is done, the emergency sweep could be an
issue.  We had a bunch of stuff in XenServer in our most recent
release to try to mitigate this, but it was all pretty hacky and
unsuitable for upstreaming.  I determined that it just needs to be
re-written in a way that actually made things Better; I haven't gotten
a chance to do that yet.

It looks like ATM the sweep is limited to doing 2MiB at a time; so if
you have a reasonably sized guest, every other superpage that gets hit
will cause another sweep -- potentially a big problem.

I have a patch that attempts to greedily re-grab pages after a sweep;
I'll check to see if it applies to tip, and if so, I'll send it to you
to see if that helps any.

 -George

  parent reply	other threads:[~2011-05-16 10:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-15 10:16 what happens when a PoD page is touched? James Harper
2011-05-16  8:39 ` Tim Deegan
2011-05-16  9:16   ` Paul Durrant
2011-05-16  9:21     ` James Harper
2011-05-16  9:17   ` James Harper
2011-05-16  9:39     ` Tim Deegan
2011-05-16  9:21   ` Paul Durrant
2011-05-16  9:22     ` James Harper
2011-05-16  9:27       ` Paul Durrant
2011-05-16 23:39         ` James Harper
2011-05-17  9:28           ` Paul Durrant
2011-05-17  9:37             ` James Harper
2011-05-17 13:00               ` George Dunlap
2011-05-18  4:52                 ` James Harper
2011-05-18  5:20                   ` James Harper
2011-05-18 10:23                   ` Jan Beulich
2011-05-17 11:32             ` George Dunlap
2011-05-16 10:05       ` George Dunlap [this message]
2011-05-16 23:42         ` James Harper

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='BANLkTimG+HK=dWm-w9M6LirhFxaiWy532A@mail.gmail.com' \
    --to=george.dunlap@eu.citrix.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=Tim.Deegan@eu.citrix.com \
    --cc=james.harper@bendigoit.com.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).