From: Andre Przywara <andre.przywara@amd.com>
To: Stefan de Konink <stefan@konink.de>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Migration and Node parameter
Date: Mon, 6 Oct 2008 21:40:53 +0200 [thread overview]
Message-ID: <48EA69C5.5000705@amd.com> (raw)
In-Reply-To: <48EA0BEC.6070308@konink.de>
Stefan de Konink wrote:
> def domain_migrate(self, domid, dst, live=False, port=0, node=-1,
> ssl=None):
> """Start domain migration.
> ...
> @keyword node: use node number for target
> @type node: int
> ...
> What does the node parameter do in this context?
This means the NUMA node the new guest should be created on. Newer Xen
versions create guests on a single node and choose the least used one.
If later the system load changes, it can become imbalanced in respect to
equal load on all nodes. In this situation you can manually move a guest
to another NUMA node. (NUMA literature often uses the term "NUMA domain"
instead of node, but for obvious reason I try to avoid this term in Xen)
Using localhost migration for this purpose isn't the smartest solution,
but was fairly easy to implement ... and works.
See unstable c/s 17148 for the code.
Regards,
Andre.
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 277-84917
----to satisfy European Law for business letters:
AMD Saxony Limited Liability Company & Co. KG,
Wilschdorfer Landstr. 101, 01109 Dresden, Germany
Register Court Dresden: HRA 4896, General Partner authorized
to represent: AMD Saxony LLC (Wilmington, Delaware, US)
General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy
prev parent reply other threads:[~2008-10-06 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 13:00 Migration and Node parameter Stefan de Konink
2008-10-06 19:40 ` Andre Przywara [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=48EA69C5.5000705@amd.com \
--to=andre.przywara@amd.com \
--cc=stefan@konink.de \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.