similar to: [PATCH] virtio_balloon: coding style fixes

On Thu 15-01-15 13:39:06, Michael S. Tsirkin wrote: > Most of our code has > struct foo { > } > > Fix two instances where balloon is inconsistent. I hate to complain but is it really necessary to post such patches to linux-api? I thought the list was primarily for API related discussions. This is not the only mail sent here which doesn't fall into that category IMO. It is far

On Thu 15-01-15 13:39:06, Michael S. Tsirkin wrote: > Most of our code has > struct foo { > } > > Fix two instances where balloon is inconsistent. I hate to complain but is it really necessary to post such patches to linux-api? I thought the list was primarily for API related discussions. This is not the only mail sent here which doesn't fall into that category IMO. It is far

On Thu, Jan 15, 2015 at 02:06:42PM +0100, Michal Hocko wrote: > On Thu 15-01-15 13:39:06, Michael S. Tsirkin wrote: > > Most of our code has > > struct foo { > > } > > > > Fix two instances where balloon is inconsistent. > > I hate to complain but is it really necessary to post such patches to > linux-api? Well it's human to err, so it seems wise to

On Thu, Jan 15, 2015 at 02:06:42PM +0100, Michal Hocko wrote: > On Thu 15-01-15 13:39:06, Michael S. Tsirkin wrote: > > Most of our code has > > struct foo { > > } > > > > Fix two instances where balloon is inconsistent. > > I hate to complain but is it really necessary to post such patches to > linux-api? Well it's human to err, so it seems wise to

Excessive virtio_balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. Various mechanisms are responsible for correct virtio_balloon memory management. Nevertheless it is often the case that these control tools does not have enough time to react on fast changing memory load. As a result OS runs out of memory and invokes OOM-killer. The balancing of

Excessive virtio_balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. Various mechanisms are responsible for correct virtio_balloon memory management. Nevertheless it is often the case that these control tools does not have enough time to react on fast changing memory load. As a result OS runs out of memory and invokes OOM-killer. The balancing of

On Thursday, March 16, 2017 3:09 PM Wei Wang wrote: > The implementation of the current virtio-balloon is not very efficient, because > the ballooned pages are transferred to the host one by one. Here is the > breakdown of the time in percentage spent on each step of the balloon inflating > process (inflating 7GB of an 8GB idle guest). > > 1) allocating pages (6.5%) > 2)

On Thursday, March 16, 2017 3:09 PM Wei Wang wrote: > The implementation of the current virtio-balloon is not very efficient, because > the ballooned pages are transferred to the host one by one. Here is the > breakdown of the time in percentage spent on each step of the balloon inflating > process (inflating 7GB of an 8GB idle guest). > > 1) allocating pages (6.5%) > 2)

On Fri, Jun 15, 2018 at 12:43:11PM +0800, Wei Wang wrote: > Negotiation of the VIRTIO_BALLOON_F_FREE_PAGE_HINT feature indicates the > support of reporting hints of guest free pages to host via virtio-balloon. > > Host requests the guest to report free page hints by sending a command > to the guest via setting the VIRTIO_BALLOON_HOST_CMD_FREE_PAGE_HINT bit > of the host_cmd

On Fri, Jun 15, 2018 at 12:43:11PM +0800, Wei Wang wrote: > Negotiation of the VIRTIO_BALLOON_F_FREE_PAGE_HINT feature indicates the > support of reporting hints of guest free pages to host via virtio-balloon. > > Host requests the guest to report free page hints by sending a command > to the guest via setting the VIRTIO_BALLOON_HOST_CMD_FREE_PAGE_HINT bit > of the host_cmd

On Wednesday, April 5, 2017 11:54 AM, Michael S. Tsirkin wrote: > On Wed, Apr 05, 2017 at 03:31:36AM +0000, Wang, Wei W wrote: > > On Thursday, March 16, 2017 3:09 PM Wei Wang wrote: > > > The implementation of the current virtio-balloon is not very > > > efficient, because the ballooned pages are transferred to the host > > > one by one. Here is the breakdown

On Wednesday, April 5, 2017 11:54 AM, Michael S. Tsirkin wrote: > On Wed, Apr 05, 2017 at 03:31:36AM +0000, Wang, Wei W wrote: > > On Thursday, March 16, 2017 3:09 PM Wei Wang wrote: > > > The implementation of the current virtio-balloon is not very > > > efficient, because the ballooned pages are transferred to the host > > > one by one. Here is the breakdown

On Fri, Jun 15, 2018 at 02:11:23PM +0000, Wang, Wei W wrote: > On Friday, June 15, 2018 7:42 PM, Michael S. Tsirkin wrote: > > On Fri, Jun 15, 2018 at 12:43:11PM +0800, Wei Wang wrote: > > > Negotiation of the VIRTIO_BALLOON_F_FREE_PAGE_HINT feature indicates > > > the support of reporting hints of guest free pages to host via virtio-balloon. > > > > >

On Fri, Jun 15, 2018 at 02:11:23PM +0000, Wang, Wei W wrote: > On Friday, June 15, 2018 7:42 PM, Michael S. Tsirkin wrote: > > On Fri, Jun 15, 2018 at 12:43:11PM +0800, Wei Wang wrote: > > > Negotiation of the VIRTIO_BALLOON_F_FREE_PAGE_HINT feature indicates > > > the support of reporting hints of guest free pages to host via virtio-balloon. > > > > >

This patch series is separated from the previous "Virtio-balloon Enhancement" series. The new feature, VIRTIO_BALLOON_F_FREE_PAGE_HINT, implemented by this series enables the virtio-balloon driver to report hints of guest free pages to the host. It can be used to accelerate live migration of VMs. Here is an introduction of this usage: Live migration needs to transfer the VM's

This patch series is separated from the previous "Virtio-balloon Enhancement" series. The new feature, VIRTIO_BALLOON_F_FREE_PAGE_HINT, implemented by this series enables the virtio-balloon driver to report hints of guest free pages to the host. It can be used to accelerate live migration of VMs. Here is an introduction of this usage: Live migration needs to transfer the VM's

From: Raushaniya Maksudova <rmaksudova at parallels.com> Excessive virtio_balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. Various mechanisms are responsible for correct virtio_balloon memory management. Nevertheless it is often the case that these control tools does not have enough time to react on fast changing memory load. As a result OS

From: Raushaniya Maksudova <rmaksudova at parallels.com> Excessive virtio_balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. Various mechanisms are responsible for correct virtio_balloon memory management. Nevertheless it is often the case that these control tools does not have enough time to react on fast changing memory load. As a result OS

This patch series is separated from the previous "Virtio-balloon Enhancement" series. The new feature, VIRTIO_BALLOON_F_FREE_PAGE_HINT, implemented by this series enables the virtio-balloon driver to report hints of guest free pages to the host. It can be used to accelerate live migration of VMs. Here is an introduction of this usage: Live migration needs to transfer the VM's

This patch series is separated from the previous "Virtio-balloon Enhancement" series. The new feature, VIRTIO_BALLOON_F_FREE_PAGE_HINT, implemented by this series enables the virtio-balloon driver to report hints of guest free pages to the host. It can be used to accelerate live migration of VMs. Here is an introduction of this usage: Live migration needs to transfer the VM's