On Mon, May 13, 2013 at 02:25:11PM -0400, Luiz Capitulino wrote: > On Mon, 13 May 2013 11:34:41 -0300 > Rafael Aquini <aqu...@redhat.com> wrote: > > > You're right, and the host's member is used to communicate the configured > > size > > to guest's balloon device, however, by not changing it when the shrinker > > causes > > the balloon to deflate will make the balloon thread to be woken up again > > in order to chase the balloon size target again, won't it? Check > > I don't see the balloon thread waking up after the shrinker executes in my > testing. Maybe this is so because it will only wake up when QEMU notifies > a config change.
Well that's also a problem. Need some mechanism to re-inflate balloon when guest memory pressure is down. virtio fs mechanism worth a look? > But anyway, I'll think how to improve this as suggested by Michael too, as > I seem to be changing num_pages' semantics according to the virtio spec. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
