Balloon device is frequently used as a mean of cooperative memory control
in between guest and host to manage memory overcommitment. This is the
typical case for any hosting workload when KVM guest is provided for
end-user.
Though there is a problem in this setup. The end-user and hosting
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
and rename it to release_pages_balloon. The function originally takes
arrays of pfns and now it takes pointer to struct virtio_ballon.
This change is necessary to conditionally call adjust_managed_page_count
in the next patch.
Signed-off-by: Denis V. Lunev d...@openvz.org
CC: Michael S. Tsirkin
On 08/19/2015 07:54 PM, Victor Kaplansky wrote:
On Mon, Aug 17, 2015 at 10:43:46AM +0800, Jason Wang wrote:
On 08/16/2015 09:42 PM, Victor Kaplansky wrote:
Clarify general description of the mac, status and
max_virtqueue_pairs fields. Specifically, the old description is
vague about
On 08/19/2015 07:31 PM, Victor Kaplansky wrote:
On Mon, Aug 17, 2015 at 11:07:15AM +0800, Jason Wang wrote:
On 08/16/2015 09:42 PM, Victor Kaplansky wrote:
@@ -3128,6 +3134,7 @@ struct virtio_net_config {
u8 mac[6];
le16 status;
le16 max_virtqueue_pairs;
+
Sorry, forgot to Cc Michael and the virt list - patch reproduced below
in full.
johannes
From 22500fbcf722748fe3471b2e4c6156db47aade15 Mon Sep 17 00:00:00 2001
From: Johannes Berg johannes.b...@intel.com
Date: Wed, 19 Aug 2015 09:25:18 +0200
Subject: [PATCH] virtio_net: use DECLARE_EWMA
Instead
