All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Nolan <nolan@sigbus.net>
Cc: kvm@vger.kernel.org
Subject: Re: Live memory allocation?
Date: Sun, 29 Mar 2009 15:33:40 +0300	[thread overview]
Message-ID: <49CF6AA4.2060108@redhat.com> (raw)
In-Reply-To: <loom.20090328T181813-137@post.gmane.org>

Nolan wrote:
> Windows does zero all memory at boot, and also runs a idle-priority thread in
> the background to zero memory as it is freed.  This way it is far less likely to
> need to zero a page to satisfy a memory allocation request.  Whether or not this
> is still a win now that people care about power consumption is an open question.
>
> I suspect the difference of behavior between KVM and VMware is related to
> VMware's page sharing.  All those zeroed pages can be collapsed into one COW
> zero page.  I wouldn't be surprised to learn that VMware has heuristics in the
> page sharing code specifically for windows guests.
>
> Perhaps KSM would help you?  Alternately, a heuristic that scanned for (and
> collapsed) fully zeroed pages when a page is faulted in for the first time could
> catch these.
>   

ksm will indeed collapse these pages.  Lighter-weight alternatives exist 
-- ballooning (need a Windows driver), or, like you mention, a simple 
scanner that looks for zero pages and drops them.  That could be 
implemented within qemu (with some simple kernel support for dropping 
zero pages atomically, say madvise(MADV_DROP_IFZERO).

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-03-29 12:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 13:44 Live memory allocation? Evert
2009-03-26 14:01 ` Tomasz Chmielewski
2009-03-26 14:04   ` Izik Eidus
2009-03-26 14:11     ` Tomasz Chmielewski
2009-03-26 17:47       ` Evert
2009-03-28 13:38       ` Alberto Treviño
2009-03-28 17:17         ` Brian Jackson
2009-03-30 13:23           ` Alberto Treviño
2009-03-30 15:48             ` Brian Jackson
2009-03-28 18:25         ` Nolan
2009-03-29 12:33           ` Avi Kivity [this message]
2009-03-30 13:40             ` Tomasz Chmielewski
2009-03-30 13:48               ` Avi Kivity
2009-03-30 13:55                 ` Tomasz Chmielewski
2009-03-30 14:58                   ` Avi Kivity
2009-03-30 15:15                     ` Tomasz Chmielewski
2009-03-30 15:18                       ` Javier Guerra
2009-03-31  9:30                         ` Tomasz Chmielewski

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=49CF6AA4.2060108@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=nolan@sigbus.net \
    /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.