From: Yanfei Xu <isyanfei.xu@gmail.com>
To: Jinpu Wang <jinpu.wang@cloud.ionos.com>,
Yanfei Xu <yanfei.xu@bytedance.com>
Cc: qemu-devel@nongnu.org, peterx@redhat.com, farosas@suse.de,
lizhijian@fujitsu.com, fangying.tommy@bytedance.com,
caixiangfeng@bytedance.com
Subject: Re: [PATCH v3 0/4] migration/rdma: Allow multiple writes per chunk
Date: Mon, 14 Sep 2026 13:40:46 +0800 [thread overview]
Message-ID: <7d0c9385-e278-4361-88b6-55971731fb87@gmail.com> (raw)
In-Reply-To: <CAMGffEmorCT_swNfGqZJvHyfYk7pZBPier-qu3NaFjXf-sE8vA@mail.gmail.com>
On 2026/9/14 13:04, Jinpu Wang wrote:
> Hi Yanfei,
>
> FYI, I ran a quick migration test on our test machines and didn't
> notice any issues with the v2 patchset. We saw a 10–12% downtime
> reduction on our setup (100 Gb/s dual-port IB fabric, 100 GB VM, idle
> load).
>
> As v3 don't change the implementation.
> Tested-by: Jack Wang <jinpu.wang@cloud.ionos.com>
Thanks Jinpu!
Yanfei
>
> Best regards,
> Jinpu Wang
next prev parent reply other threads:[~2026-09-14 5:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 6:24 [PATCH v3 0/4] migration/rdma: Allow multiple writes per chunk Yanfei Xu
2026-09-13 6:24 ` [PATCH v3 1/4] migration/ram: Add RAM round synchronization notifiers Yanfei Xu
2026-09-13 6:24 ` [PATCH v3 2/4] migration/rdma: Drain writes at RAM round boundaries Yanfei Xu
2026-09-13 6:24 ` [PATCH v3 3/4] migration/rdma: Allow multiple in-flight writes per chunk Yanfei Xu
2026-09-13 6:24 ` [PATCH v3 4/4] migration/rdma: Remove unused transit bitmap Yanfei Xu
2026-09-14 5:04 ` [PATCH v3 0/4] migration/rdma: Allow multiple writes per chunk Jinpu Wang
2026-09-14 5:40 ` Yanfei Xu [this message]
2026-09-22 12:37 ` Fabiano Rosas
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=7d0c9385-e278-4361-88b6-55971731fb87@gmail.com \
--to=isyanfei.xu@gmail.com \
--cc=caixiangfeng@bytedance.com \
--cc=fangying.tommy@bytedance.com \
--cc=farosas@suse.de \
--cc=jinpu.wang@cloud.ionos.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.