From: Yanfei Xu <isyanfei.xu@gmail.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Li Zhijian <lizhijian@fujitsu.com>,
Samuel Zhang <guoqing.zhang@amd.com>,
Fabiano Rosas <farosas@suse.de>, Jack Wang <jinpu.wang@ionos.com>,
Juraj Marcin <jmarcin@redhat.com>,
Yanfei Xu <yanfei.xu@bytedance.com>
Subject: Re: [PATCH 02/10] migration/rdma: Remove unregister code
Date: Wed, 19 Aug 2026 11:55:40 +0800 [thread overview]
Message-ID: <c1695bbf-3ce1-45c3-a73a-047ba0fdc433@gmail.com> (raw)
In-Reply-To: <aoRvobhlj6-YJsqT@x1.local>
On 2026/8/18 22:43, Peter Xu wrote:
> I actually don't know why RDMA_CONTROL_COMPRESS is only used in !pin_all,
> do you know?
my understanding is that with RDMA_CONTROL_COMPRESS, the corresponding MR
isn't registered, so the memset(0) in destination side can be guaranteed to
complete before the next RDMA write to the same chunk. Or it needs an
extra ack from destionation for the memset(0) complation.
>
> I can only guess RDMA WRITEs were fast and need no round-robin chats, so
> it's faster than RDMA_CONTROL_COMPRESS, but you seem to say it's not true.
if most of guest's pages are not being allocated yet or are zero page,
RDMA_CONTROL_COMPRESS works more efficient.
>
> Meanwhile, I would expect pin-all=off ultimately should meet the same perf
> over pin-all=on.. so I don't really know how needs pin-all=on... maybe
> it's useful when one is looking for minimum total migration time when VMs
> are required to be evicted from one host?
>
> Feel free to share if you have more data points; I'm almost speaking from
> reading the code, so it could be wrong.
Hah, I am new to RDMA live migration, glad to discuss ^_^
Yanfei
next prev parent reply other threads:[~2026-08-19 3:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 20:24 [PATCH 00/10] migration/rdma: Fixes or drops Peter Xu
2026-08-17 20:24 ` [PATCH 01/10] migration/rdma: Introduce RDMA_CONTROL_NUM Peter Xu
2026-08-19 10:35 ` Jinpu Wang
2026-08-17 20:24 ` [PATCH 02/10] migration/rdma: Remove unregister code Peter Xu
2026-08-18 11:57 ` Yanfei Xu
2026-08-18 13:01 ` Peter Xu
2026-08-18 13:57 ` Yanfei Xu
2026-08-18 14:43 ` Peter Xu
2026-08-19 3:55 ` Yanfei Xu [this message]
2026-08-19 10:52 ` Jinpu Wang
2026-08-19 12:01 ` Jinpu Wang
2026-08-19 12:47 ` Peter Xu
2026-08-17 20:24 ` [PATCH 03/10] migration/rdma: Stick with rdma_ prefix for all tracepoints Peter Xu
2026-08-19 11:39 ` Jinpu Wang
2026-08-17 20:24 ` [PATCH 04/10] migration/rdma: Drop RDMALocalBlock.is_ram_block Peter Xu
2026-08-19 12:43 ` Jinpu Wang
2026-08-17 20:24 ` [PATCH 05/10] migration/rdma: Drop RDMALocalBlock.unregister_bitmap Peter Xu
2026-08-19 12:44 ` Jinpu Wang
2026-08-17 20:24 ` [PATCH 06/10] migration/rdma: Drop RDMARegister.key.chunk Peter Xu
2026-08-19 12:48 ` Jinpu Wang
2026-08-17 20:24 ` [PATCH 07/10] migration/rdma: Sanity check RDMA_CONTROL_REGISTER_REQUEST on buflen Peter Xu
2026-08-19 12:52 ` Jinpu Wang
2026-08-17 20:24 ` [PATCH 08/10] migration/rdma: Sanity check RDMA_CONTROL_REGISTER_REQUEST chunks Peter Xu
2026-08-19 13:00 ` Jinpu Wang
2026-08-17 20:24 ` [PATCH 09/10] migration/rdma: Sanity check upper bound of register MR address Peter Xu
2026-08-19 13:09 ` Jinpu Wang
2026-08-17 20:24 ` [PATCH 10/10] migration/rdma: Sanity check compress request ranges Peter Xu
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=c1695bbf-3ce1-45c3-a73a-047ba0fdc433@gmail.com \
--to=isyanfei.xu@gmail.com \
--cc=farosas@suse.de \
--cc=guoqing.zhang@amd.com \
--cc=jinpu.wang@ionos.com \
--cc=jmarcin@redhat.com \
--cc=lizhijian@fujitsu.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yanfei.xu@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.