From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Lidong Chen <jemmy858585@gmail.com>
Cc: quintela@redhat.com, qemu-devel@nongnu.org, adido@mellanox.com,
licq@mellanox.com, Lidong Chen <lidongchen@tencent.com>
Subject: Re: [Qemu-devel] [PATCH 0/5] Enable postcopy RDMA live migration
Date: Wed, 11 Apr 2018 13:29:24 +0100 [thread overview]
Message-ID: <20180411122923.GE2667@work-vm> (raw)
In-Reply-To: <1523089594-1422-1-git-send-email-lidongchen@tencent.com>
* Lidong Chen (jemmy858585@gmail.com) wrote:
> Current Qemu RDMA communication does not support send and receive
> data at the same time, so when RDMA live migration with postcopy
> enabled, the source qemu return path thread get qemu file error.
>
> Those patch add the postcopy support for RDMA live migration.
This description is a little misleading; it doesn't really
do RDMA during the postcopy phase - what it really does is disable
the RDMA page sending during the postcopy phase, relying on the
RDMA codes stream emulation to send the page.
That's not necessarily a bad fix; you get the nice performance of RDMA
during the precopy phase, but how bad are you finding the performance
during the postcopy phase - the RDMA code we have was only really
designed for sending small commands over the stream?
Dave
> Lidong Chen (5):
> migration: create a dedicated connection for rdma return path
> migration: add the interface to set get_return_path
> migration: implement the get_return_path for RDMA iochannel
> migration: fix qemu carsh when RDMA live migration
> migration: disable RDMA WRITR after postcopy started.
>
> migration/qemu-file-channel.c | 12 ++--
> migration/qemu-file.c | 13 +++-
> migration/qemu-file.h | 2 +-
> migration/rdma.c | 148 ++++++++++++++++++++++++++++++++++++++++--
> 4 files changed, 163 insertions(+), 12 deletions(-)
>
> --
> 1.8.3.1
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-04-11 12:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 8:26 [Qemu-devel] [PATCH 0/5] Enable postcopy RDMA live migration Lidong Chen
2018-04-07 8:26 ` [Qemu-devel] [PATCH 1/5] migration: create a dedicated connection for rdma return path Lidong Chen
2018-04-11 16:57 ` Dr. David Alan Gilbert
2018-04-07 8:26 ` [Qemu-devel] [PATCH 2/5] migration: add the interface to set get_return_path Lidong Chen
2018-04-11 17:18 ` Dr. David Alan Gilbert
2018-04-12 8:28 ` Daniel P. Berrangé
2018-04-12 10:08 ` 858585 jemmy
2018-04-07 8:26 ` [Qemu-devel] [PATCH 3/5] migration: implement the get_return_path for RDMA iochannel Lidong Chen
2018-04-07 8:26 ` [Qemu-devel] [PATCH 4/5] migration: fix qemu carsh when RDMA live migration Lidong Chen
2018-04-11 16:43 ` Dr. David Alan Gilbert
2018-04-12 9:40 ` 858585 jemmy
2018-04-12 18:58 ` Dr. David Alan Gilbert
2018-04-07 8:26 ` [Qemu-devel] [PATCH 5/5] migration: disable RDMA WRITR after postcopy started Lidong Chen
2018-04-11 15:56 ` Dr. David Alan Gilbert
2018-04-12 6:50 ` 858585 jemmy
2018-04-12 18:55 ` Dr. David Alan Gilbert
2018-04-09 1:05 ` [Qemu-devel] [PATCH 0/5] Enable postcopy RDMA live migration 858585 jemmy
2018-04-11 12:29 ` Dr. David Alan Gilbert [this message]
2018-04-12 3:57 ` 858585 jemmy
2018-04-24 13:36 ` Dr. David Alan Gilbert
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=20180411122923.GE2667@work-vm \
--to=dgilbert@redhat.com \
--cc=adido@mellanox.com \
--cc=jemmy858585@gmail.com \
--cc=licq@mellanox.com \
--cc=lidongchen@tencent.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).