From: George Dunlap <george.dunlap@eu.citrix.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: Anil Madhavapeddy <anil@recoil.org>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
xen-devel <xen-devel@lists.xen.org>,
Dario Faggioli <raistlin@linux.it>,
Jan Beulich <JBeulich@suse.com>,
Yang Z Zhang <yang.z.zhang@intel.com>
Subject: Re: NUMA TODO-list for xen-devel
Date: Fri, 3 Aug 2012 12:00:46 +0100 [thread overview]
Message-ID: <501BAF5E.6080805@eu.citrix.com> (raw)
In-Reply-To: <501B9E81.1020302@amd.com>
On 03/08/12 10:48, Andre Przywara wrote:
>>> I think we could use cpu hot-plug to change the "virtual topology" of
>>> VMs, couldn't we? We could probably even do that on a running guest
>>> if we really needed to.
>> Hmm, not sure - using hotplug behind the back of the guest might
>> be possible, but you'd first need to hot-unplug the vCPU. That's
>> something that I don't think you can do on HVM guests (and for
>> PV guests, guest visible NUMA support makes even less sense
>> than for HVM ones).
> I don't think that hotplug would really work. I have checked this some
> times ago, at least the Linux NUMA code cannot be really fooled by this.
> The SRAT table is firmware defined and static by nature, so there is no
> code in Linux to change the NUMA topology at runtime. This is especially
> true for the memory layout.
I was more thinking of giving a VM the biggest topology you would want
at boot, and then asking Linux to online or offline vcpus; for example,
giving it a 4x2 topology (4 vcores x 2 vnodes). When running on a
system with 2 cores per node, you offline 2 vcpus per vnode, giving it
an effective layout of 2x2. When running on a system with 4 cores per
node, you could offline all of the cores on one node, giving it an
effective topology of 4x1.
Unfortunately, I just realized that you could change the number of vcpus
in a given node, but you couldn't move the memory around very easily.
Unless you have memory hotplug? Hmm..... :-)
-George
next prev parent reply other threads:[~2012-08-03 11:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 16:16 NUMA TODO-list for xen-devel Dario Faggioli
2012-08-01 16:24 ` Dario Faggioli
2012-08-01 16:30 ` Andrew Cooper
2012-08-01 16:47 ` Dario Faggioli
2012-08-01 16:53 ` Andrew Cooper
2012-08-02 9:40 ` Jan Beulich
2012-08-02 13:21 ` Dario Faggioli
2012-08-01 16:32 ` Anil Madhavapeddy
2012-08-01 16:58 ` Dario Faggioli
2012-08-02 0:04 ` Malte Schwarzkopf
2012-08-07 23:53 ` Dario Faggioli
2012-08-02 1:04 ` Zhang, Yang Z
2012-08-07 22:56 ` Dario Faggioli
2012-08-02 9:43 ` Jan Beulich
2012-08-02 13:34 ` Dario Faggioli
2012-08-02 14:07 ` Jan Beulich
2012-08-02 16:36 ` George Dunlap
2012-08-03 9:23 ` Jan Beulich
2012-08-03 9:48 ` Andre Przywara
2012-08-03 10:03 ` Jan Beulich
2012-08-03 22:40 ` Dan Magenheimer
2012-08-03 11:00 ` George Dunlap [this message]
2012-08-03 22:34 ` Dan Magenheimer
2012-08-06 7:15 ` Jan Beulich
2012-08-06 16:28 ` Dan Magenheimer
2012-08-03 10:02 ` Andre Przywara
2012-08-03 10:40 ` Jan Beulich
2012-08-03 11:26 ` Andre Przywara
2012-08-03 11:38 ` Jan Beulich
2012-08-03 13:14 ` Dario Faggioli
2012-08-03 13:52 ` Jan Beulich
2012-08-03 22:42 ` Dan Magenheimer
2012-08-08 7:07 ` Dario Faggioli
2012-08-08 7:43 ` Dario Faggioli
2012-08-03 22:22 ` Dan Magenheimer
2012-08-07 23:49 ` 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=501BAF5E.6080805@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=andre.przywara@amd.com \
--cc=anil@recoil.org \
--cc=raistlin@linux.it \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.com \
/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).