xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Joshua Otto <jtotto@uwaterloo.ca>,
	hongyang.yang@easystack.cn, xen-devel@lists.xen.org
Cc: hjarmstr@uwaterloo.ca, czylin@uwaterloo.ca
Subject: Re: Taking on a Xen development project
Date: Sat, 12 Dec 2015 23:02:50 +0000	[thread overview]
Message-ID: <566CA79A.5020009@citrix.com> (raw)
In-Reply-To: <20151212223051.GA17350@personal>

On 12/12/2015 22:30, Joshua Otto wrote:
> On Sat, Dec 12, 2015 at 10:19:31AM +0800, Yang Hongyang wrote:
>> On 2015年12月11日 01:23, Andrew Cooper wrote:
>>> Hello - thankyou for your interest.
>>>
>>> One area to look at might be the parameters to the live migration
>>> looping.  As part of the migration v2 rework I did in the 4.6 dev
>>> period, I left all of that alone, and it is in a working but poor state.
>>>
>>> In the past, there have been several research investigations into
>>> improving the live migration algorithm, such as tracking the rate of
>>> dirtying of memory, or attempting to resume the domain on the far side
>>> and fault the final memory across.
>> I think you mean postcopy here? The hypervisor then needs to maintain
>> a dirty page bitmap and generate pagefault when a page is not yet
>> tranferred to the far end.
>> This feature already merged into QEMU2.5(kvm patch which generates
>> pagefault also been merged into linux kernel mainline), if you want a
>> reference, you can take a look at those patches.
>> This surely is a great aera to work on.
>>
>>> If you are interested in perusing this, start with reading
>>> docs/features/migration.pandoc in the Xen tree.
> We'd definitely be interested in working on live migration!  The feature
> is essentially an implementation of the approach described in Section
> 5.1 of [0], right?

Yes - Section 5.1 is quite a good general description of live migration
(even after my white-room redesign from first principles), although be
aware that some of the more technical details are now out of date.

>
> Would the focus of the project be to implement and evaluate postcopy
> live migration in Xen, then, or to more generally build on previous
> research efforts? (either way sounds like fun!)

I hadn't really though that far ahead.  I was more suggestion that the
general area of live migration has a lot in the way to offer for
projects, be it implementing someone else's research, or researching a
new area yourself.

There are definitely areas where improvements can be made, and some of
these would be an easier introduction to the codebase than to start with
a full postcopy implementation.  (Not that I wish to put you off
postcopy, but it does come with a number of non-trivial problems to
solve as part of getting the scaffolding in place.)

I guess it depends on what you are looking to get out of a project like
this, and what timescale you have.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2015-12-12 23:02 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 20:26 Taking on a Xen development project jtotto
2015-12-10 10:59 ` Wei Liu
2015-12-10 17:23 ` Andrew Cooper
2015-12-12  2:19   ` Yang Hongyang
2015-12-12 22:30     ` Joshua Otto
2015-12-12 23:02       ` Andrew Cooper [this message]
2015-12-14 22:49         ` Joshua Otto
2015-12-11 13:52 ` Ian Campbell
2015-12-12 22:07   ` Joshua Otto
2015-12-14 11:08     ` Ian Campbell
2015-12-14 22:59       ` Joshua Otto
2015-12-15 15:48         ` Ian Campbell
2015-12-28  5:16       ` Coverity tidying Joshua Otto
2015-12-28  5:16         ` [PATCH 1/5] libxl: tidy libxl_get_scheduler() according to CODING_STYLE Joshua Otto
2016-01-04 16:23           ` Ian Campbell
2016-01-05  8:20             ` Dario Faggioli
2016-01-19  5:57               ` [PATCH v2 " Chester Lin
2016-01-19  9:14                 ` Dario Faggioli
2016-01-19 11:28                 ` Wei Liu
2016-01-19 11:35                   ` Ian Campbell
2015-12-28  5:16         ` [PATCH 2/5] libxl: make GC_FREE reachable in libxl_get_scheduler() Joshua Otto
2016-01-04 16:29           ` Ian Campbell
2016-01-05  8:49             ` Dario Faggioli
2016-01-05 11:16               ` Ian Campbell
2016-01-19  5:57                 ` [PATCH v2 " Chester Lin
2016-01-19  9:08                   ` Dario Faggioli
2016-01-19 14:15                   ` Ian Jackson
2015-12-28  5:16         ` [PATCH 3/5] ns16550: widen an integer constant for Coverity Joshua Otto
2016-01-04 16:36           ` Ian Campbell
2016-01-06  9:26             ` Jan Beulich
2016-01-19  5:57               ` [PATCH v2 3/5] n16550: add sanity check for reg_shift Chester Lin
2016-01-19 13:32                 ` Jan Beulich
2016-01-25  0:41                   ` czylin
2015-12-28  5:16         ` [PATCH 4/5] credit: remove pointless local variable initialization Joshua Otto
2015-12-28  5:16         ` [PATCH 5/5] libxl: Add explicit cast to libxl_psr_cat_set_cbm Joshua Otto
2016-01-04 16:40           ` Ian Campbell
2016-01-19  5:58             ` [PATCH v2 " Chester Lin
2016-01-19  8:34               ` Dario Faggioli
2016-01-19 14:06               ` Ian Jackson
2016-01-19 14:21                 ` Ian Campbell
2016-01-19 14:28                   ` Dario Faggioli
2016-01-19 14:33                     ` Ian Jackson
2016-01-19 14:31                   ` George Dunlap
2016-01-19 14:31                 ` Ian Campbell
2016-01-19 14:35                   ` Ian Jackson
2017-01-12 18:08                     ` George Dunlap
2017-01-13  9:05                       ` Dario Faggioli
2015-12-28  9:34         ` Coverity tidying Andrew Cooper
2016-01-01  3:14           ` [PATCH] svm: rephrase local variable use for Coverity Joshua Otto
2016-01-06 13:24             ` Jan Beulich
2016-01-06 14:33               ` Boris Ostrovsky

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=566CA79A.5020009@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=czylin@uwaterloo.ca \
    --cc=hjarmstr@uwaterloo.ca \
    --cc=hongyang.yang@easystack.cn \
    --cc=jtotto@uwaterloo.ca \
    --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 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).