Re: [Xen-devel] [PATCH 2/2] libxl: xl mem-set should not enforce memory limits

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

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.

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).

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel