From: Dario Faggioli <dario.faggioli@citrix.com>
To: Kun Cheng <chengkunck@gmail.com>
Cc: Frediano Ziglio <freddy77@gmail.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Could Xen hyperviosr be able to invoke Linux systemcalls?
Date: Wed, 19 Aug 2015 11:27:29 -0700 [thread overview]
Message-ID: <1440008849.2772.16.camel@citrix.com> (raw)
In-Reply-To: <CAO3v1VRmcA5rrMnAS7GLTEVwNNSkcOHqWXivDEufK2T=vMikcA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1416 bytes --]
On Wed, 2015-08-19 at 00:47 +0000, Kun Cheng wrote:
> Live migration between nodes is perhaps the easiest way. But it also
> has draw backs mainly because that migration is coarse-grained.
>
What I'm saying is that you can, as a first step, look at the migration
code and implement (let's call it so) page moving in a similar way. That
does not mean that you'd have to *always* move all the pages, like a
migration does, you well can move only one page, or a bunch of them.
It's the mechanism for implementing that you should take inspiration
from.
> Supposing that a VM has multiple VCPUs, if only some of them are
> moved to another node or some other nodes. Then it will be tough to
> decide which one should be the target node for the live migration.
>
A policy needs to be defined, sure. But we're not talking about that,
we're talking about, after you've decided what to do, how to do that.
> However, I also think live migration is the best 'first step'. But
> finally a fine grained memory migration is the destination. By the
> way, I am currently digging the migration code. ;)
>
Great! :-)
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
prev parent reply other threads:[~2015-08-19 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 1:31 Could Xen hyperviosr be able to invoke Linux systemcalls? Kun Cheng
2015-08-16 16:16 ` Frediano Ziglio
2015-08-17 0:55 ` Kun Cheng
2015-08-17 19:25 ` Dario Faggioli
2015-08-18 1:18 ` Kun Cheng
2015-08-18 9:16 ` Dario Faggioli
2015-08-19 0:47 ` Kun Cheng
2015-08-19 18:27 ` Dario Faggioli [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=1440008849.2772.16.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=chengkunck@gmail.com \
--cc=freddy77@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.