xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: keir@xen.org, Ian.Campbell@citrix.com,
	stefano.stabellini@eu.citrix.com, lccycc123@gmail.com,
	ian.jackson@eu.citrix.com, xen-devel@lists.xen.org,
	JBeulich@suse.com, sw@linux.com,
	Elena Ufimtseva <ufimtseva@gmail.com>
Subject: Re: [PATCH RFC v2 0/7] xen: vNUMA introduction
Date: Fri, 13 Sep 2013 14:25:48 +0200	[thread overview]
Message-ID: <1379075148.6095.34.camel@Solace> (raw)
In-Reply-To: <5232F4A6.9050303@eu.citrix.com>


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

On ven, 2013-09-13 at 12:19 +0100, George Dunlap wrote:
> > NUMA machine:
> > cpu_topology           :
> > cpu:    core    socket     node
> >    0:       0        0        0
> >    1:       1        0        0
> >    2:       2        0        0
> >    3:       3        0        0
> >    4:       0        1        1
> >    5:       1        1        1
> >    6:       2        1        1
> >    7:       3        1        1
> > numa_info              :
> > node:    memsize    memfree    distances
> >     0:     17664      12243      10,20
> >     1:     16384      11929      20,10
> >
> > VM config:
> >
> > memory = 16384
> > vcpus = 8
> > name = "rcbig"
> > vnodes = 8
> > vnumamem = "2g, 2g, 2g, 2g, 2g, 2g, 2g, 2g"
> > vcpu_to_vnode ="5 6 7 4 3 2 1 0"
> 
> This was a bit confusing for me as the table above and the config below 
> don't seem to be the same.
> 
I think the table refers to the host.

However, as it came out already in other messages, I think we seriously
need some good interface, with talking names and a well specified
default behavior for any possible combination of parameters for this
stuff, or it will be impossible to use properly!!

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-09-13 12:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13  8:49 [PATCH RFC v2 0/7] xen: vNUMA introduction Elena Ufimtseva
2013-09-13 10:38 ` Jan Beulich
2013-09-13 11:12   ` Dario Faggioli
2013-09-13 12:00     ` Jan Beulich
2013-09-13 11:19 ` George Dunlap
2013-09-13 12:25   ` 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=1379075148.6095.34.camel@Solace \
    --to=dario.faggioli@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=lccycc123@gmail.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=sw@linux.com \
    --cc=ufimtseva@gmail.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).