xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Jim Fehlig <jfehlig@suse.com>, Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: [libvirt] [PATCH 1/4] libxl: implement NUMA capabilities reporting
Date: Thu, 4 Jul 2013 19:29:54 +0200	[thread overview]
Message-ID: <1372958994.10336.106.camel@Solace> (raw)
In-Reply-To: <1e5b54d2-2999-46cd-ad50-33b12249d512@email.android.com>


[-- Attachment #1.1: Type: text/plain, Size: 1413 bytes --]

On gio, 2013-07-04 at 13:21 -0400, Konrad Rzeszutek Wilk wrote:
> Dario Faggioli <dario.faggioli@citrix.com> wrote:
>
> >On lun, 2013-07-01 at 16:47 -0600, Jim Fehlig wrote:
> >> info --numa' says
> >> 
> >> total_memory           : 8190
> >> ...
> >> numa_info              :
> >> node:    memsize    memfree    distances
> >>     0:      8960       7116      10
> >> 
> >> Why is the node memsize > total_memory?
> >
> >Mmm... Interesting question. I really never paid attention to this...
> >Jan (or anyone else), is that something known and/or expected?
> >
> Is the difference not the amount that Xen hypervisor consumes?  It just has not been subtracted from the NUMA values. 
>
I thought about that too, and I'm not that has nothing to do with it.

However, in the rest of my message, I reported the results of some
investigation I did, and the relevant (and hopefully correct enough)
calculations... Have you seen that? What do you think about it?

Moreover, wherever the difference is coming from, what I'm asking is,
should we stick with this situation or take some kind of action?

Thanks and 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

      reply	other threads:[~2013-07-04 17:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130628142948.28579.8536.stgit@hit-nxdomain.opendns.com>
     [not found] ` <20130628143244.28579.57535.stgit@hit-nxdomain.opendns.com>
     [not found]   ` <51D206FB.8000908@suse.com>
2013-07-04 16:53     ` [libvirt] [PATCH 1/4] libxl: implement NUMA capabilities reporting Dario Faggioli
2013-07-04 17:21       ` Konrad Rzeszutek Wilk
2013-07-04 17:29         ` Dario Faggioli [this message]

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=1372958994.10336.106.camel@Solace \
    --to=dario.faggioli@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=jfehlig@suse.com \
    --cc=konrad.wilk@oracle.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).