xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Juergen Gross <juergen.gross@ts.fujitsu.com>,
	xen-devel <xen-devel@lists.xen.org>,
	Jan Beulich <JBeulich@suse.com>,
	Daniel De Graaf <dgdegra@tycho.nsa.gov>
Subject: Re: [PATCH 2/4] libxc: report how much memory a domain has on each NUMA node
Date: Mon, 10 Mar 2014 18:07:30 +0100	[thread overview]
Message-ID: <1394471250.17832.11.camel@Solace> (raw)
In-Reply-To: <21277.60093.406016.679465@mariner.uk.xensource.com>


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

On lun, 2014-03-10 at 16:39 +0000, Ian Jackson wrote:
> Dario Faggioli writes ("[PATCH 2/4] libxc: report how much memory a domain has on each NUMA node"):
> > by means of a new interface: xc_domain_numainfo().
> > 
> > The caller is expected to allocate an array for the call to fill,
> > with the results of the XEN_DOMCTL_numainfo hypercall. The size of
> > the array is also passed to the function, which then returns back
> > the number of elements that have actually been filled by Xen.
> 
> Is there a need to get this data in a way which is coherent with the
> domain info list memory usage data ?
> 
You mean the output of `xl list' and `xl list -l'? I mean, these:

root@Zhaman:~# xl list 1
Name                                        ID   Mem VCPUs	State	Time(s)
vm-test                                      1  4096    16     -b----       6.8

root@Zhaman:~# xl list -l 1
[
    ...
            "b_info": {
                ...
                "max_memkb": 4194304,
                "target_memkb": 4194304,
                "video_memkb": -1,
                "shadow_memkb": 49152,
    ...
]

?

If yes, I think it is coherent, and if not, yes, it should be and that's
a bug... have you found any occurrences of such thing?

> What are callers supposed to do about discrepancies between the two
> sets of information ?
>
I'm sorry, what discrepancies?

root@Zhaman:~# xl numainfo 1
NODE Affinity: all
Memory:
  Node 0: 2097152 Kb
  Node 1: 2097152 Kb

root@Zhaman:~# bc -l
bc 1.06.95
2097152+2097152
4194304

Or was it something else you where talking about?

> (I forget: is the choice of node to allocate memory from up to the
> guest, or the hose ?  
>
It's up to the toolstack. Then, something that can happen is that Xen
does not have enough memory on the specified nodes, but that's another
story.

> Is there any way to say a guest can use no more
> than X1 amount on node 1 and no more than X2 on node 2 ?)
> 
There is no now, but that's a nice addition, and there will be soon, as,
for instance, Elena had it implemented already, for the sake of vNUMA
(but it can be used in non-vNUMA contexts too).

Did I answer your questions?

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:[~2014-03-10 17:07 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 14:36 [PATCH 0/4] report how much memory a domain has on each NUMA node Dario Faggioli
2014-03-05 14:36 ` [PATCH 1/4] xen: " Dario Faggioli
2014-03-05 14:50   ` Juergen Gross
2014-03-05 16:31     ` Dario Faggioli
2014-03-05 16:49       ` Jan Beulich
2014-03-05 17:14         ` Dario Faggioli
2014-03-05 15:04   ` Jan Beulich
2014-03-05 16:13     ` Dario Faggioli
2014-03-05 16:44       ` Jan Beulich
2014-03-05 14:36 ` [PATCH 2/4] libxc: " Dario Faggioli
2014-03-05 15:05   ` Andrew Cooper
2014-03-05 15:40     ` Dario Faggioli
2014-03-10 16:39   ` Ian Jackson
2014-03-10 17:07     ` Dario Faggioli [this message]
2014-03-10 17:09       ` Andrew Cooper
2014-03-10 17:20       ` Ian Jackson
2014-03-10 17:35         ` Dario Faggioli
2014-03-11 11:15           ` Ian Jackson
2014-03-11 17:37             ` Dario Faggioli
2014-03-11 18:16               ` Ian Jackson
2014-03-11 19:04                 ` Dario Faggioli
2014-03-13 11:54                   ` George Dunlap
2014-03-05 14:36 ` [PATCH 3/4] libxl: " Dario Faggioli
2014-03-10 16:40   ` Ian Jackson
2014-03-10 17:28     ` Dario Faggioli
2014-03-13 17:26       ` Ian Jackson
2014-03-05 14:36 ` [PATCH 4/4] xl: " Dario Faggioli
2014-03-10 16:42   ` Ian Jackson
2014-03-10 17:09     ` Dario Faggioli
2014-03-05 14:40 ` [PATCH 0/4] " Juergen Gross
2014-03-05 14:44   ` Dario Faggioli
2014-03-10 16:37 ` Ian Jackson
2014-03-10 17:12   ` 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=1394471250.17832.11.camel@Solace \
    --to=dario.faggioli@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=juergen.gross@ts.fujitsu.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).