xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Dario Faggioli <dario.faggioli@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: Spurious "NUMA placement failed, performance might be affected" message on ARM
Date: Mon, 28 Apr 2014 13:15:29 +0100	[thread overview]
Message-ID: <535E4661.70700@citrix.com> (raw)
In-Reply-To: <1398684642.29700.71.camel@kazak.uk.xensource.com>

On 28/04/14 12:30, Ian Campbell wrote:
> On Mon, 2014-04-28 at 11:01 +0100, Ian Campbell wrote:
> [...]
>> total_memory           : 8184
>> free_memory            : 6933
> [...]
>> node:    memsize    memfree    distances
>>    0:      4088       3861      20
> I think we are missing some RAM here...
>
> and I have now noticed that I only see this for guests which have more
> RAM than this memfree value (+/- some slop). The guests succeed because
> there is actually RAM available.
>
> I think this is enough for me to now track down the cause on the
> hypervisor side. Thanks for your input.
>
> Ian.

Do be aware that the memsize value is "number of pages on this node"
which includes IO mappings of non-ram regions, and as a result memfree
is mostly fictitious.

I raised this as a concern with the hwloc code, but without any
subsequent discussion.

~Andrew

  reply	other threads:[~2014-04-28 12:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 10:37 Spurious "NUMA placement failed, performance might be affected" message on ARM Ian Campbell
2014-04-28  9:55 ` Dario Faggioli
2014-04-28 10:01   ` Ian Campbell
2014-04-28 10:25     ` Dario Faggioli
2014-04-28 11:30     ` Ian Campbell
2014-04-28 12:15       ` Andrew Cooper [this message]
2014-04-29 15:36         ` Dario Faggioli
2014-04-28 12:23       ` Dario Faggioli

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=535E4661.70700@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=dario.faggioli@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).