From: Dario Faggioli <raistlin@linux.it>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andre Przywara <andre.przywara@amd.com>,
Anil Madhavapeddy <anil@recoil.org>,
George Dunlap <dunlapg@gmail.com>,
xen-devel <xen-devel@lists.xen.org>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
Yang Z Zhang <yang.z.zhang@intel.com>
Subject: Re: NUMA TODO-list for xen-devel
Date: Thu, 02 Aug 2012 15:34:50 +0200 [thread overview]
Message-ID: <1343914490.4873.18.camel@Solace> (raw)
In-Reply-To: <501A67C502000078000921FF@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 2279 bytes --]
On Thu, 2012-08-02 at 10:43 +0100, Jan Beulich wrote:
> >>> On 01.08.12 at 18:16, Dario Faggioli <raistlin@linux.it> wrote:
> > - Virtual NUMA topology exposure to guests (a.k.a guest-numa). If a
> > guest ends up on more than one nodes, make sure it knows it's
> > running on a NUMA platform (smaller than the actual host, but
> > still NUMA). This interacts with some of the above points:
>
> The question is whether this is really useful beyond the (I would
> suppose) relatively small set of cases where migration isn't
> needed.
>
Mmm... Not sure I'm getting what you're saying here, sorry. Are you
suggesting that exposing a virtual topology is not a good idea as it
poses constraints/prevents live migration?
If yes, well, I mostly agree that this is an huge issue, and that's why
I think wee need some bright idea on how to deal with it. I mean, it's
easy to make it optional and let it automatically disable migration,
giving users the choice what they prefer, but I think this is more
dodging the problem than dealing with it! :-P
> > * consider this during automatic placement for
> > resuming/migrating domains (if they have a virtual topology,
> > better not to change it);
> > * consider this during memory migration (it can change the
> > actual topology, should we update it on-line or disable memory
> > migration?)
>
> The question is whether trading functionality for performance
> is an acceptable choice.
>
Indeed. Again, I think it is possible to implement things flexibly
enough, but then we need to come out with a sane default, so we're not
allowed to avoid discussing and deciding on this.
One can argue that it is an issue only for big-enough guests (and/or
nearly overcommitted hosts) that don't fit in only one node (as, if they
do, there is no virtual topology to export), but I'm not sure we can
neglect them on this basis.
Thanks for the feedback,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/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:[~2012-08-02 13:34 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 [this message]
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
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=1343914490.4873.18.camel@Solace \
--to=raistlin@linux.it \
--cc=Andrew.Cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=andre.przywara@amd.com \
--cc=anil@recoil.org \
--cc=dunlapg@gmail.com \
--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).