From: Dario Faggioli <dario.faggioli@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: Spurious "NUMA placement failed, performance might be affected" message on ARM
Date: Tue, 29 Apr 2014 17:36:19 +0200 [thread overview]
Message-ID: <1398785779.16933.23.camel@Solace> (raw)
In-Reply-To: <535E4661.70700@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1632 bytes --]
On lun, 2014-04-28 at 13:15 +0100, Andrew Cooper wrote:
> 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.
>
There has been another discussion about discrepancies in total and free
memory reporting. ISTR, it was noticed at the time when I added the
support for some of these NUMA stuff in libvirt.
I don't have it handy right now... I'll see if I can fetch it back,
merge it with your observations in the hwloc thread and (re)start a
discussion about this.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-04-29 15:36 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
2014-04-29 15:36 ` Dario Faggioli [this message]
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=1398785779.16933.23.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=andrew.cooper3@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.