From: Jules <junqing.wang@cs2c.com.cn>
To: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
Cc: pbonzini@redhat.com,
Juan Jose Quintela Carreira <quintela@redhat.com>,
"Michael R. Hines" <mrhines@us.ibm.com>,
qemu-devel@nongnu.org, owasserm@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/4] Curling: KVM Fault Tolerance
Date: Wed, 23 Oct 2013 13:23:11 +0800 [thread overview]
Message-ID: <1382505791.1720.30.camel@localhost> (raw)
In-Reply-To: <5266E75F.9060300@linux.vnet.ibm.com>
On 2013-10-22 17:00 -0400,Michael R. Hines wrote:
> On 10/15/2013 03:26 AM, Jules Wang wrote:
> > v2 -> v3:
> > * add documentation of new option in qapi-schema.
> >
> > * long option name: ft -> fault-tolerant
> >
> > v1 -> v2:
> > * cmdline: migrate curling:tcp:<address>:<port>
> > -> migrate -f tcp:<address>:<port>
> >
> > * sender: use QEMU_VM_FILE_MAGIC_FT as the header of the migration
> > to indicate this is a ft migration.
> >
> > * receiver: look for the signature:
> > QEMU_VM_EOF_MAGIC + QEMU_VM_FILE_MAGIC_FT(64bit total)
> > which indicates the end of one migration.
> > --
> > Jules Wang (4):
> > Curling: add doc
> > Curling: cmdline interface.
> > Curling: the sender
> > Curling: the receiver
> >
> > arch_init.c | 25 ++++--
> > docs/curling.txt | 51 ++++++++++++
> > hmp-commands.hx | 10 ++-
> > hmp.c | 3 +-
> > include/migration/migration.h | 1 +
> > include/migration/qemu-file.h | 1 +
> > include/sysemu/sysemu.h | 5 +-
> > migration.c | 50 ++++++++++--
> > qapi-schema.json | 6 +-
> > qmp-commands.hx | 3 +-
> > savevm.c | 178 +++++++++++++++++++++++++++++++++++++++---
> > 11 files changed, 303 insertions(+), 30 deletions(-)
> > create mode 100644 docs/curling.txt
> >
>
> Jules, I think we should work together. The patches I sent this week
> solve all of the problems (and more) of Kemari and have been in
> testing for over 1 year.
>
> 1. I/O buffering is already working
> 2. Checkpoint parallelism is already working
> 3. Staging of the checkpoint memory is already working
> on both the sender side and receiver side.
> 3. Checkpoint chunking is already working (this means that checkpoints
> can be very large and must be split up like slab caches,
> which can dynamically grow and shrink as the amount of
> diryt memory in the virtual machine fluctuates.
> 4. RDMA checkpointing is already working
> 5. TCP checkpointing is already working
> 6. There does not need to be a custom migration URI
> - this is easily implemented through a capability.
> 7. Libvirt support is already available on github.
> 8 There is no need to modify the QEMU migration metadata state information.
>
> All of these features take advantage of the recent advances
> in QEMU in migration performance improvements over the last
> few years.
I will read your patches carefully as a good learning material.
>
> Would you be interested in "joining forces"? You even picked
> a cool name (I didn't even choose a name)..... =)
Yes, your solution is better than mine obviously, and we could work
together to improve your patches.
>
> Also: I will soon be working in IBM China Beijing, for 3 years - starting
> next month - perhaps we could talk on the phone (or meet in person)?
Welcome to Beijing and take some dust masks with you, you will need
them. :)
I prefer email or meet in person if necessary. I will read and try your
patches first.
> - Michael
>
>
>
next prev parent reply other threads:[~2013-10-23 5:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 7:26 [Qemu-devel] [PATCH v3 0/4] Curling: KVM Fault Tolerance Jules Wang
2013-10-15 7:26 ` [Qemu-devel] [PATCH v3 1/4] Curling: add doc Jules Wang
2013-10-17 11:25 ` Stefan Hajnoczi
2013-10-15 7:26 ` [Qemu-devel] [PATCH v3 2/4] Curling: cmdline interface Jules Wang
2013-10-15 7:26 ` [Qemu-devel] [PATCH v3 3/4] Curling: the sender Jules Wang
2013-10-15 7:26 ` [Qemu-devel] [PATCH v3 4/4] Curling: the receiver Jules Wang
2013-10-17 11:50 ` [Qemu-devel] [PATCH v3 0/4] Curling: KVM Fault Tolerance Stefan Hajnoczi
2013-10-23 0:08 ` Jules
2013-10-24 12:10 ` Stefan Hajnoczi
2013-10-22 21:00 ` Michael R. Hines
2013-10-23 5:23 ` Jules [this message]
2013-11-06 18:38 ` Michael R. Hines
2013-10-22 21:08 ` Michael R. Hines
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=1382505791.1720.30.camel@localhost \
--to=junqing.wang@cs2c.com.cn \
--cc=mrhines@linux.vnet.ibm.com \
--cc=mrhines@us.ibm.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).