From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: keir@xen.org, Ian.Campbell@citrix.com, lccycc123@gmail.com,
george.dunlap@eu.citrix.com, stefano.stabellini@eu.citrix.com,
ian.jackson@eu.citrix.com, Elena Ufimtseva <ufimtseva@gmail.com>,
xen-devel <xen-devel@lists.xenproject.org>,
sw@linux.com
Subject: Re: [PATCH RFC v2 0/7] xen: vNUMA introduction
Date: Fri, 13 Sep 2013 13:12:31 +0200 [thread overview]
Message-ID: <1379070751.6095.27.camel@Solace> (raw)
In-Reply-To: <5233073002000078000F3083@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1940 bytes --]
On ven, 2013-09-13 at 11:38 +0100, Jan Beulich wrote:
> >>> On 13.09.13 at 10:49, Elena Ufimtseva <ufimtseva@gmail.com> wrote:
> > 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"
>
> For an example it would probably be useful to use a more traditional
> case, i.e. more than one vCPU per vNode.
>
Right... Perhaps Elena could post another example with such
characteristics, to show us what happens in that case? (And of course
use that for the cover letter of next version too :-P)
> Also, the settings above say nothing about the relationship to
> physical nodes, yet that's an important aspect for VM creation.
> Are you perhaps implying that each vNode would get assigned
> to a tool stack chosen pNode?
>
Yep. So, right now, I don't think there is a way to specify an explicit
virtual to physical mapping, and what happens is exactly that: the
toolstack picks. However, I indeed agree that we want to introduce
something like that, to give the user full control, if he's interested
in it.
That being said, I also think that, if the user does not say anything
about that, having the toolstack choosing is a sane default.
> What if there are more vNodes
> than pNodes?
>
That is the actual issue, from an UI perspective, on which I'd like some
discussion to happen... I'll send an e-mail with some more details on
that later.
> What if node distances vary, and the admin wants
> some control over the placement?
>
Again, I totally agree: we should provide such mechanism.
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
next prev parent reply other threads:[~2013-09-13 11:12 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 [this message]
2013-09-13 12:00 ` Jan Beulich
2013-09-13 11:19 ` George Dunlap
2013-09-13 12:25 ` 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=1379070751.6095.27.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.xenproject.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).