Displaying 4 results from an estimated 4 matches for "virtio_ballon".
Did you mean:
virtio_balloon
2015 Sep 09
0
[PULL] vhost: cleanups and fixes
...ns.
total memory is better reported when using virtio balloon with auto-deflate.
cache control is re-enabled when using virtio-blk in modern mode.
Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
----------------------------------------------------------------
Denis V. Lunev (2):
virtio_ballon: change stub of release_pages_by_pfn
virtio_balloon: do not change memory amount visible via /proc/meminfo
Fam Zheng (1):
virtio-blk: Allow extended partitions
Graeme Gregory (1):
virtio_mmio: add ACPI probing
Paolo Bonzini (1):
virtio-blk: use VIRTIO_BLK_F_WCE and VIRTIO...
2015 Sep 09
0
[PULL] vhost: cleanups and fixes
...ns.
total memory is better reported when using virtio balloon with auto-deflate.
cache control is re-enabled when using virtio-blk in modern mode.
Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
----------------------------------------------------------------
Denis V. Lunev (2):
virtio_ballon: change stub of release_pages_by_pfn
virtio_balloon: do not change memory amount visible via /proc/meminfo
Fam Zheng (1):
virtio-blk: Allow extended partitions
Graeme Gregory (1):
virtio_mmio: add ACPI probing
Paolo Bonzini (1):
virtio-blk: use VIRTIO_BLK_F_WCE and VIRTIO...
2015 Aug 19
2
[PATCH 0/2] virtio_balloon: do not change memory amount visible via /proc/meminfo
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.
2015 Aug 19
2
[PATCH 0/2] virtio_balloon: do not change memory amount visible via /proc/meminfo
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.