Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755202Ab3EMTK0 (ORCPT ); Mon, 13 May 2013 15:10:26 -0400 Received: from mx1.redhat.com ([209.132.183.28]:30677 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753636Ab3EMTKY (ORCPT ); Mon, 13 May 2013 15:10:24 -0400 Message-ID: <51913A9B.2030807@redhat.com> Date: Mon, 13 May 2013 15:10:19 -0400 From: Rik van Riel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130402 Thunderbird/17.0.5 MIME-Version: 1.0 To: "Michael S. Tsirkin" CC: Luiz Capitulino , linux-mm@kvack.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, aquini@redhat.com, amit.shah@redhat.com, anton@enomsg.org Subject: Re: [RFC 2/2] virtio_balloon: auto-ballooning support References: <1368111229-29847-1-git-send-email-lcapitulino@redhat.com> <1368111229-29847-3-git-send-email-lcapitulino@redhat.com> <20130512143054.GI10144@redhat.com> <518FC4F9.5010505@redhat.com> <20130512184934.GA16334@redhat.com> <20130513110303.33dbaba6@redhat.com> <20130513151624.GB1992@redhat.com> <51910552.5050507@redhat.com> <20130513153513.GA4981@redhat.com> In-Reply-To: <20130513153513.GA4981@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1236 Lines: 29 On 05/13/2013 11:35 AM, Michael S. Tsirkin wrote: > On Mon, May 13, 2013 at 11:22:58AM -0400, Rik van Riel wrote: >> I believe the Google patches still included some way for the >> host to initiate balloon inflation on the guest side, because >> the guest internal state alone is not enough to see when the >> host is under memory pressure. >> >> I discussed the project with the Google developers in question >> a little over a year ago, but I do not remember whether their >> pressure notification went through qemu, or directly from the >> host kernel to the guest kernel... > > So increasing the max number of pages in balloon > indicates host memory pressure to the guest? > Fair enough but I wonder whether there's a way to > make it more explicit in the interface, somehow. There may be a better way to do this, but I am really not sure what that would be. What properties would you like to see in the interface? What kind of behaviour are you looking for? -- All rights reversed -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/