From: Dario Faggioli <dario.faggioli@citrix.com>
To: Kun Cheng <chengkunck@gmail.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: VM Migration on a NUMA server?
Date: Mon, 3 Aug 2015 12:10:41 +0200 [thread overview]
Message-ID: <1438596641.16912.154.camel@citrix.com> (raw)
In-Reply-To: <CAO3v1VTy=Z3OAQRFU8HJVS_X1Loah1ZgbL+mj9fZSo-boDXG=g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1639 bytes --]
On Sat, 2015-08-01 at 06:21 +0000, Kun Cheng wrote:
> I've looked into those settings and vcpu affinities on Xen wiki page.
> However what I'm trying to argue about is memory should be migrated
> when vcpus are moved to another node.
>
I still struggle a bit to understand what you mean. It's exactly what I
said (or, at least, what I tried to do) that memory is *not* moved right
now.
There's no mean to do that, and putting one together is something really
difficult. There probably would be benefits of having it in place, but
only if it's implemented in the proper way, and applied with the proper
policing, which all should be thought, discussed and implemented.
> But setting a vcpu's affinity only seems to allow vcpu migration
> between different nodes. As my NUMA server is on the way I cannot
> verify that.
>
Well, that is correct, memory is not moved. The local migration trick,
which I described in my previous email, actually works "only" because
migrating a guest basically means re-creating it from scratch (although,
of course, the "new" guest resumes from where the "old" was when
migration started), and hence re-allocate all it's memory, rather than
moving it.
> Anyhow, moving memory really draws my interest now.
>
Glad to hear that. Feel free to give it a try, and report here what you
find out. :-)
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: 181 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:[~2015-08-03 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 2:32 VM Migration on a NUMA server? Kun Cheng
2015-07-31 11:41 ` Kun Cheng
2015-07-31 12:10 ` Wei Liu
2015-07-31 12:50 ` Dario Faggioli
2015-08-01 6:21 ` Kun Cheng
2015-08-03 10:10 ` Dario Faggioli [this message]
2015-08-03 12:23 ` Kun Cheng
2015-08-03 12:48 ` Dario Faggioli
2015-07-31 12:46 ` Dario Faggioli
2015-07-31 15:51 ` Kun Cheng
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=1438596641.16912.154.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=chengkunck@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 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.