From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [PATCH] RFC: initial libxl support for xenpaging Date: Fri, 17 Feb 2012 16:43:47 +0100 Message-ID: <20120217154346.GA19731@aepfle.de> References: <1329486241.3131.81.camel@zakaz.uk.xensource.com> <20120217142505.GA10523@aepfle.de> <1329490712.3131.97.camel@zakaz.uk.xensource.com> <20120217152443.GA16995@aepfle.de> <1329492796.3131.104.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1329492796.3131.104.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Fri, Feb 17, Ian Campbell wrote: > On Fri, 2012-02-17 at 15:24 +0000, Olaf Hering wrote: > > Where do you see the complexity? > > For users in determining what changing a given value will actually do, > what values they need to use to get the behaviour which they want, what > happens if they change first one value and then the other, how do they > interact with mem-set and memmax, what are the various invalid or > meaningless combinations etc. > > There's also complexity for us in trying to decide what the right answer > is to each of those questions and trying to implement it in a consistent > way and explain it all to users. A figure like the one in tools/libxl/libxl_memory.txt will explain it very well, if done right. Perhaps I should write up something based on that figure. Olaf