From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rik van Riel Subject: Re: [PATCH] Add a page cache-backed balloon device driver. Date: Mon, 10 Sep 2012 14:04:08 -0400 Message-ID: <504E2B98.3010007@redhat.com> References: <1340742778-11282-1-git-send-email-fes@google.com> <20120910090521.GB18544@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Mike Waychison Cc: Frank Swiderski , Andrea Arcangeli , kvm@vger.kernel.org, "Michael S. Tsirkin" , "linux-kernel@vger.kernel.org" , virtualization@lists.linux-foundation.org List-Id: virtualization@lists.linuxfoundation.org On 09/10/2012 01:37 PM, Mike Waychison wrote: > On Mon, Sep 10, 2012 at 5:05 AM, Michael S. Tsirkin wrote: >> Also can you pls answer Avi's question? >> How is overcommit managed? > > Overcommit in our deployments is managed using memory cgroups on the > host. This allows us to have very directed policies as to how > competing VMs on a host may overcommit. How do your memory cgroups lead to guests inflating their balloons? -- All rights reversed