From: 858585 jemmy <jemmy858585@gmail.com>
To: zhang.zhanghailiang@huawei.com,
Juan Quintela <quintela@redhat.com>,
Dave Gilbert <dgilbert@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Lidong Chen <lidongchen@tencent.com>
Subject: Re: [Qemu-devel] [PATCH v6 00/12] Enable postcopy RDMA live migration
Date: Mon, 6 Aug 2018 14:09:49 +0800 [thread overview]
Message-ID: <CAOGPPbfpO9WYDLLdRC7dyaCr_Evmb6v=O5Wm6tgDPXpw7o7zdQ@mail.gmail.com> (raw)
In-Reply-To: <1533287630-4221-1-git-send-email-lidongchen@tencent.com>
There is one compile error, please ignore those patch, I will send a
new version patch.
On Fri, Aug 3, 2018 at 5:13 PM, Lidong Chen <jemmy858585@gmail.com> wrote:
> The RDMA QIOChannel does not support bi-directional communication, so when RDMA
> live migration with postcopy enabled, the source qemu return path get qemu file
> error.
>
> These patches implement bi-directional communication for RDMA QIOChannel and
> disable the RDMA WRITE during the postcopy phase.
>
> This patch just make postcopy works, and will improve performance later.
>
> [v6]
> - rebase
> - add the check whether release rdma resource has finished(David)
> - remove unnecessary RDMA_CONTROL_ERROR when cleanup(David)
> - poll the cm event for destination qemu
>
> [v5]
> - rebase
> - fix bug for create a dedicated thread to release rdma resource(David)
> - fix bug for poll the cm event while wait RDMA work request completion(David,Gal)
>
> [v4]
> - not wait RDMA_CM_EVENT_DISCONNECTED event after rdma_disconnect
> - implement io_set_aio_fd_handler function for RDMA QIOChannel (Juan Quintela)
> - invoke qio_channel_yield only when qemu_in_coroutine() (Juan Quintela)
> - create a dedicated thread to release rdma resource
> - poll the cm event while wait RDMA work request completion
> - implement the shutdown function for RDMA QIOChannel
>
> [v3]
> - add a mutex in QEMUFile struct to avoid concurrent channel close (Daniel)
> - destroy the mutex before free QEMUFile (David)
> - use rdmain and rmdaout instead of rdma->return_path (Daniel)
>
> [v2]
> - does not update bytes_xfer when disable RDMA WRITE (David)
> - implement bi-directional communication for RDMA QIOChannel (Daniel)
>
> Lidong Chen (12):
> migration: disable RDMA WRITE after postcopy started
> migration: create a dedicated connection for rdma return path
> migration: avoid concurrent invoke channel_close by different threads
> migration: implement bi-directional RDMA QIOChannel
> migration: Stop rdma yielding during incoming postcopy
> migration: implement io_set_aio_fd_handler function for RDMA
> QIOChannel
> migration: invoke qio_channel_yield only when qemu_in_coroutine()
> migration: poll the cm event while wait RDMA work request completion
> migration: implement the shutdown for RDMA QIOChannel
> migration: poll the cm event for destination qemu
> migration: remove the unnecessary RDMA_CONTROL_ERROR message
> migration: create a dedicated thread to release rdma resource
>
> migration/colo.c | 2 +
> migration/migration.c | 13 +-
> migration/migration.h | 10 +
> migration/postcopy-ram.c | 2 +
> migration/qemu-file-channel.c | 12 +-
> migration/qemu-file.c | 14 +-
> migration/ram.c | 4 +
> migration/rdma.c | 448 ++++++++++++++++++++++++++++++++++++++----
> migration/savevm.c | 3 +
> 9 files changed, 458 insertions(+), 50 deletions(-)
>
> --
> 1.8.3.1
>
prev parent reply other threads:[~2018-08-06 6:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 9:13 [Qemu-devel] [PATCH v6 00/12] Enable postcopy RDMA live migration Lidong Chen
2018-08-03 9:13 ` [Qemu-devel] [PATCH v6 01/12] migration: disable RDMA WRITE after postcopy started Lidong Chen
2018-08-03 9:13 ` [Qemu-devel] [PATCH v6 02/12] migration: create a dedicated connection for rdma return path Lidong Chen
2018-08-03 9:13 ` [Qemu-devel] [PATCH v6 03/12] migration: avoid concurrent invoke channel_close by different threads Lidong Chen
2018-08-06 9:07 ` 858585 jemmy
2018-08-03 9:13 ` [Qemu-devel] [PATCH v6 04/12] migration: implement bi-directional RDMA QIOChannel Lidong Chen
2018-08-03 9:13 ` [Qemu-devel] [PATCH v6 05/12] migration: Stop rdma yielding during incoming postcopy Lidong Chen
2018-08-03 9:13 ` [Qemu-devel] [PATCH v6 06/12] migration: implement io_set_aio_fd_handler function for RDMA QIOChannel Lidong Chen
2018-08-03 9:13 ` [Qemu-devel] [PATCH v6 07/12] migration: invoke qio_channel_yield only when qemu_in_coroutine() Lidong Chen
2018-08-03 9:13 ` [Qemu-devel] [PATCH v6 08/12] migration: poll the cm event while wait RDMA work request completion Lidong Chen
2018-08-03 9:13 ` [Qemu-devel] [PATCH v6 09/12] migration: implement the shutdown for RDMA QIOChannel Lidong Chen
2018-08-03 9:13 ` [Qemu-devel] [PATCH v6 10/12] migration: poll the cm event for destination qemu Lidong Chen
2018-08-03 9:13 ` [Qemu-devel] [PATCH v6 11/12] migration: remove the unnecessary RDMA_CONTROL_ERROR message Lidong Chen
2018-08-03 9:13 ` [Qemu-devel] [PATCH v6 12/12] migration: create a dedicated thread to release rdma resource Lidong Chen
2018-08-03 9:42 ` [Qemu-devel] [PATCH v6 00/12] Enable postcopy RDMA live migration no-reply
2018-08-06 6:09 ` 858585 jemmy [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='CAOGPPbfpO9WYDLLdRC7dyaCr_Evmb6v=O5Wm6tgDPXpw7o7zdQ@mail.gmail.com' \
--to=jemmy858585@gmail.com \
--cc=dgilbert@redhat.com \
--cc=lidongchen@tencent.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=zhang.zhanghailiang@huawei.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).