From: "Denis V. Lunev" <den@openvz.org>
To: unlisted-recipients:; (no To-header on input)
Cc: virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, "Denis V. Lunev" <den@openvz.org>,
Igor Redko <redkoi@virtuozzo.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/2] export 'available' memory to virtio balloon statistics
Date: Tue, 16 Feb 2016 18:50:50 +0300 [thread overview]
Message-ID: <1455637852-7323-1-git-send-email-den@openvz.org> (raw)
Add a new field, VIRTIO_BALLOON_S_AVAIL, to virtio_balloon memory
statistics protocol, corresponding to 'Available' in /proc/meminfo.
It indicates to the hypervisor how big the balloon can be inflated
without pushing the guest system to swap. This metric would be very
useful in VM orchestration software to improve memory management
of different VMs under overcommit.
Signed-off-by: Igor Redko <redkoi@virtuozzo.com>
Reviewed-by: Roman Kagan <rkagan@virtuozzo.com>
Signed-off-by: Denis V. Lunev <den@openvz.org>
CC: Michael S. Tsirkin <mst@redhat.com>
CC: Andrew Morton <akpm@linux-foundation.org>
Igor Redko (2):
calculate 'available' memory in the separate function
virtio_balloon: export 'available' memory to balloon statistics
drivers/virtio/virtio_balloon.c | 6 ++++++
fs/proc/meminfo.c | 31 +-------------------------
include/linux/mm.h | 1 +
include/uapi/linux/virtio_balloon.h | 3 ++-
mm/page_alloc.c | 43 +++++++++++++++++++++++++++++++++++++
5 files changed, 53 insertions(+), 31 deletions(-)
--
2.5.0
next reply other threads:[~2016-02-16 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 15:50 Denis V. Lunev [this message]
2016-02-16 15:50 ` [PATCH 1/2] calculate 'available' memory in the separate function Denis V. Lunev
2016-02-16 15:50 ` [PATCH 2/2] virtio_balloon: export 'available' memory to balloon statistics Denis V. Lunev
2016-02-23 15:10 ` Michael S. Tsirkin
2016-02-23 15:26 ` Denis V. Lunev
2016-02-23 15:53 ` Michael S. Tsirkin
2016-02-23 16:12 ` Denis V. Lunev
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=1455637852-7323-1-git-send-email-den@openvz.org \
--to=den@openvz.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=redkoi@virtuozzo.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
all inboxes | Powered by JetHome®