From: "lizhijian@fujitsu.com" <lizhijian@fujitsu.com>
To: "lizhijian@fujitsu.com" <lizhijian@fujitsu.com>,
"quintela@redhat.com" <quintela@redhat.com>,
"dgilbert@redhat.com" <dgilbert@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH 0/2] enable fsdax rdma migration
Date: Mon, 16 Aug 2021 02:10:24 +0000 [thread overview]
Message-ID: <a05a6c79-3990-1303-2a9a-e6895920a322@fujitsu.com> (raw)
In-Reply-To: <20210731140332.8701-1-lizhijian@cn.fujitsu.com>
ping...
Hey Dave, could you help to take a look :)
Thanks
Zhijian
On 31/07/2021 22:03, Li Zhijian wrote:
> Previous qemu face 2 problems when migrating a fsdax memory backend with
> RDMA protocol.
> (1) ibv_reg_mr failed with Operation not supported
> (2) requester(source) side could receive RNR NAK.
>
> For the (1), we can try to register memory region with ODP feature which
> has already been implemented in some modern HCA hardware/drivers.
> For the (2), IB provides advise API to prefetch pages in specific memory
> region. It can help driver reduce the page fault on responder(destination)
> side during RDMA_WRITE.
>
> Li Zhijian (2):
> migration/rdma: Try to register On-Demand Paging memory region
> migration/rdma: advise prefetch write for ODP region
>
> migration/rdma.c | 67 ++++++++++++++++++++++++++++++++++++------
> migration/trace-events | 2 ++
> 2 files changed, 60 insertions(+), 9 deletions(-)
>
prev parent reply other threads:[~2021-08-16 2:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 14:03 [PATCH 0/2] enable fsdax rdma migration Li Zhijian
2021-07-31 14:03 ` [PATCH 1/2] migration/rdma: Try to register On-Demand Paging memory region Li Zhijian
2021-08-22 8:53 ` Marcel Apfelbaum
2021-08-23 1:41 ` lizhijian
2021-08-23 7:03 ` Marcel Apfelbaum
2021-07-31 14:03 ` [PATCH 2/2] migration/rdma: advise prefetch write for ODP region Li Zhijian
2021-08-22 8:39 ` Marcel Apfelbaum
2021-08-23 1:21 ` lizhijian
2021-08-16 2:10 ` lizhijian [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=a05a6c79-3990-1303-2a9a-e6895920a322@fujitsu.com \
--to=lizhijian@fujitsu.com \
--cc=dgilbert@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).