On 21/01/17 00:15, Jim Fehlig wrote:
> On 01/20/2017 02:54 AM, Juergen Gross wrote:
>> The information given in the xl man page for the mem-max command is
>> rather brief. Expand it in order to let the reader understand what it
>> is really doing.
>>
>> As the related libxl function libxl_domain_se
On 01/20/2017 02:54 AM, Juergen Gross wrote:
The information given in the xl man page for the mem-max command is
rather brief. Expand it in order to let the reader understand what it
is really doing.
As the related libxl function libxl_domain_setmaxmem() isn't much
clearer add a comment to it ex
On 20/01/17 16:51, Ian Jackson wrote:
> Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] [PATCH] docs: clarify xl
> mem-max semantics"):
>> On Fri, Jan 20, 2017 at 10:54:18AM +0100, Juergen Gross wrote:
>>> The mem-max value may not correspond to the actual memory
Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] [PATCH] docs: clarify xl mem-max
semantics"):
> On Fri, Jan 20, 2017 at 10:54:18AM +0100, Juergen Gross wrote:
> > The mem-max value may not correspond to the actual memory used in the
> > domain, as it may balloon down its
On Fri, Jan 20, 2017 at 10:54:18AM +0100, Juergen Gross wrote:
> The information given in the xl man page for the mem-max command is
> rather brief. Expand it in order to let the reader understand what it
> is really doing.
>
> As the related libxl function libxl_domain_setmaxmem() isn't much
> cl
The information given in the xl man page for the mem-max command is
rather brief. Expand it in order to let the reader understand what it
is really doing.
As the related libxl function libxl_domain_setmaxmem() isn't much
clearer add a comment to it explaining the desired semantics.
Signed-off-by:
