virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@openvz.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 0/2] virtio_balloon: do not change memory amount visible via /proc/meminfo
Date: Mon, 31 Aug 2015 10:33:21 +0300	[thread overview]
Message-ID: <55E40341.60500@openvz.org> (raw)
In-Reply-To: <1440020989-10824-1-git-send-email-den@openvz.org>

On 08/20/2015 12:49 AM, Denis V. Lunev wrote:
> Though there is a problem in this setup. The end-user and hosting provider
> have signed SLA agreement in which some amount of memory is guaranted for
> the guest. The good thing is that this memory will be given to the guest
> when the guest will really need it (f.e. with OOM in guest and with
> VIRTIO_BALLOON_F_DEFLATE_ON_OOM configuration flag set). The bad thing
> is that end-user does not know this.
>
> Balloon by default reduce the amount of memory exposed to the end-user
> each time when the page is stolen from guest or returned back by using
> adjust_managed_page_count and thus /proc/meminfo shows reduced amount
> of memory.
>
> Fortunately the solution is simple, we should just avoid to call
> adjust_managed_page_count with VIRTIO_BALLOON_F_DEFLATE_ON_OOM set.
>
> Please note that neither VMWare ballon nor HyperV balloon do not care
> about proper handling of adjust_managed_page_count at all.
>
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> CC: Michael S. Tsirkin <mst@redhat.com>
ping

Michael, the issue is important for us. Can you pls look?

Den

      parent reply	other threads:[~2015-08-31  7:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 21:49 [PATCH 0/2] virtio_balloon: do not change memory amount visible via /proc/meminfo Denis V. Lunev
2015-08-19 21:49 ` [PATCH 1/2] virtio_ballon: change stub of release_pages_by_pfn Denis V. Lunev
2015-08-19 21:49 ` [PATCH 2/2] virtio_balloon: do not change memory amount visible via /proc/meminfo Denis V. Lunev
2015-08-31  7:33 ` Denis V. Lunev [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=55E40341.60500@openvz.org \
    --to=den@openvz.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    /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).