From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Jackson Subject: Re: [PATCH v3 3/3] xl: Improve xl documentation in regards to guest memory management Date: Tue, 9 Apr 2013 15:33:58 +0100 Message-ID: <20836.9942.43775.304567@mariner.uk.xensource.com> References: <1365107683-25564-1-git-send-email-daniel.kiper@oracle.com> <1365107683-25564-4-git-send-email-daniel.kiper@oracle.com> <20834.60916.51889.104171@mariner.uk.xensource.com> <20130409121858.GB29064@debian70-amd64.local.net-space.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20130409121858.GB29064@debian70-amd64.local.net-space.pl> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Daniel Kiper Cc: xen-devel@lists.xensource.com, ian.campbell@citrix.com, konrad.wilk@oracle.com List-Id: xen-devel@lists.xenproject.org Daniel Kiper writes ("Re: [Xen-devel] [PATCH v3 3/3] xl: Improve xl documentation in regards to guest memory management"): > On Mon, Apr 08, 2013 at 05:19:00PM +0100, Ian Jackson wrote: > > Presumably hotplugged memory can be ballooned too. So perhaps we need > > another column ? > > I think that it is better to add comment that after > hotplugging memory could be ballooned down. I'd prefer not to make the diagram wrong. Perhaps it would be better to annotate the "static maximum" to say that it might be increased by memory hotplug. > > It might be worth adding: > > > > "Guests whose actual allocation exceeds the target may experience > > memory allocation failures." > > ... or "Guests which attempts to exceed the target may experience > memory allocation failures." No, because a guest which is being asked to shrink will experience memory allocation failures if it doesn't shrink monotonically. Ian.