From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH 2/2] libxl: xl mem-set should not enforce
 memory limits
Date: Fri, 15 Mar 2013 13:26:07 -0400
Message-ID: <20130315172607.GA14315@phenom.dumpdata.com>
References: <1363364702-12885-1-git-send-email-daniel.kiper@oracle.com>
	<1363364702-12885-3-git-send-email-daniel.kiper@oracle.com>
	<1363365173.520.33.camel@zakaz.uk.xensource.com>
	<20130315170700.GE12758@debian70-amd64.local.net-space.pl>
	<20803.21983.665377.198905@mariner.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <20803.21983.665377.198905@mariner.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Daniel Kiper <daniel.kiper@oracle.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Ian Campbell <Ian.Campbell@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Fri, Mar 15, 2013 at 05:09:51PM +0000, Ian Jackson wrote:
> Daniel Kiper writes ("Re: [PATCH 2/2] libxl: xl mem-set should not enforce memory limits"):
> > I think that xl mem-max should be used to enforce limits. If admin
> > would like to enforce "hard" limit it should call xl mem-set and
> > xl mem-max in sequence. If we would like to leave old xl mem-set
> > behavior we should change comment for this command because now
> > it does not mention anythig about limit enforcement. Or we should
> > add an option which explicitly disables memory limit enforment
> > (this behavior is in line with xm mem-set behavior).
> 
> I think this conversation is related to the fact that at Oracle you
> have a different model of the Xen memory allocation model to everyone
> else.

Daniel is trying to fix an bug that Linux kernel is tripping over
b/c of this. Look at the converstation and patch that Daniel posted
a week ago for the Linux kernel.
> 
> Outside Oracle, guests are supposed to aim for the balloon target and
> are not permitted to exceed it (when ballooning up) or to regress
> (when ballooning down).

s/Oracle/Xend/. As Xend had this distinction. 'xm mem-set' would only set
the target. 'xm mem-max' on the other hand would enforce the limit.

Daniel is just bringing this behavior to 'xl'.