From: Mike Latimer <mlatimer@suse.com>
To: xen-devel@lists.xen.org
Cc: ian.jackson@eu.citrix.com, wei.liu2@citrix.com,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: freemem-slack and large memory environments
Date: Fri, 27 Feb 2015 08:28:49 -0700 [thread overview]
Message-ID: <3226285.BhjaSCDldb@mlatimer1.dnsdhcp.provo.novell.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1502271044480.23507@kaball.uk.xensource.com>
On Friday, February 27, 2015 10:52:17 AM Stefano Stabellini wrote:
> On Thu, 26 Feb 2015, Mike Latimer wrote:
> > libxl_set_memory_target = 1
>
> The new memory target is set for dom0 successfully.
>
> > libxl_wait_for_free_memory = -5
>
> Still there isn't enough free memory in the system.
>
> > libxl_wait_for_memory_target = 0
>
> However dom0 reached the new memory target already.
> Who is stealing your memory?
I just realized I was missing commit 2048aeec, which corrects the hardcoded
return value of libxl_wait_for_memory_target from 0 to rc. I'll retest with
this change in place.
> In any case in the context of libxl_wait_for_memory_target, ERROR_FAIL
> means that the memory target has not been reached.
I'm expecting this commit to to change what I'm seeing, but I'm not convinced
it will be a good change... There is zero chance dom0 will balloon down 64GB
(or 512GB) in the 10 second window set by freemem. This will likely mean the
entire process will fail (when given a bit more time it would have succeeded).
I'll add the missing commit, and send a complete set of debug logs later
today.
-Mike
next prev parent reply other threads:[~2015-02-27 15:28 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 1:27 freemem-slack and large memory environments Mike Latimer
2015-02-10 21:34 ` Mike Latimer
2015-02-13 11:13 ` Wei Liu
2015-02-13 23:16 ` Mike Latimer
2015-02-18 14:10 ` Ian Campbell
2015-02-24 16:06 ` Stefano Stabellini
2015-02-24 16:54 ` Ian Campbell
2015-02-25 11:39 ` Stefano Stabellini
2015-02-25 12:00 ` Ian Campbell
2015-02-25 14:03 ` Ian Campbell
2015-02-25 14:09 ` Stefano Stabellini
2015-02-26 15:36 ` Mike Latimer
2015-02-26 15:57 ` Ian Campbell
2015-02-26 17:38 ` Mike Latimer
2015-02-26 17:47 ` Ian Campbell
2015-02-26 20:38 ` Mike Latimer
2015-02-27 10:17 ` Ian Campbell
2015-02-27 11:05 ` Stefano Stabellini
2015-02-26 17:53 ` Stefano Stabellini
2015-02-26 20:45 ` Mike Latimer
2015-02-26 23:30 ` Mike Latimer
2015-02-27 10:21 ` Ian Campbell
2015-02-27 10:52 ` Stefano Stabellini
2015-02-27 15:28 ` Mike Latimer [this message]
2015-02-27 18:29 ` Mike Latimer
2015-02-28 0:31 ` Mike Latimer
2015-03-02 10:12 ` Stefano Stabellini
2015-03-02 10:44 ` Jan Beulich
2015-03-02 12:13 ` Stefano Stabellini
2015-03-02 13:04 ` Jan Beulich
[not found] ` <54F46DDB020000780006505B@suse.com>
2015-03-02 22:49 ` Mike Latimer
2015-03-02 11:42 ` Ian Campbell
2015-03-02 15:19 ` Stefano Stabellini
2015-03-02 16:04 ` Ian Campbell
2015-03-02 16:15 ` Stefano Stabellini
2015-03-02 22:49 ` Mike Latimer
2015-03-03 10:02 ` Ian Campbell
2015-03-03 10:32 ` Stefano Stabellini
2015-03-03 10:40 ` Stefano Stabellini
2015-02-27 8:24 ` Jan Beulich
2015-02-27 10:52 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3226285.BhjaSCDldb@mlatimer1.dnsdhcp.provo.novell.com \
--to=mlatimer@suse.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.