From: Markus Armbruster <armbru@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Samuel Zhang <guoqing.zhang@amd.com>,
qemu-devel@nongnu.org, farosas@suse.de, lizhijian@fujitsu.com,
eblake@redhat.com, Emily.Deng@amd.com, Victor.Zhao@amd.com,
PengJu.Zhou@amd.com, Qing.Ma@amd.com
Subject: Re: [PATCH v3] migration/rdma: add x-rdma-chunk-size parameter
Date: Tue, 31 Mar 2026 13:06:37 +0200 [thread overview]
Message-ID: <875x6ctg02.fsf@pond.sub.org> (raw)
In-Reply-To: <acqgZShXRkqzBU1C@x1.local> (Peter Xu's message of "Mon, 30 Mar 2026 12:10:13 -0400")
Peter Xu <peterx@redhat.com> writes:
[...]
> One thing to mention is RDMA migration is in odd-fixes stage, actually it
> doesn't have a real maintainer so it is kind of "orphaned". In this case,
> I actually won't suggest we add any new knobs for performance reasons.
Good point.
> Do you have a strong reason to propose this patch to land upstream? Is it
> used in production systems and it solves some real problems for you?
If you use it in production, finding an upstream maintainer is in your
best interest. Give it a thought.
> I also wonder what Zhijian would say on this.
>
> Thanks,
prev parent reply other threads:[~2026-03-31 11:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 6:50 [PATCH v3] migration/rdma: add x-rdma-chunk-size parameter Samuel Zhang
2026-03-27 9:45 ` Markus Armbruster
2026-03-27 10:27 ` Zhang, GuoQing (Sam)
2026-03-27 11:24 ` Markus Armbruster
2026-03-30 16:10 ` Peter Xu
2026-03-31 3:30 ` Zhijian Li (Fujitsu)
2026-03-31 10:33 ` Zhang, GuoQing (Sam)
2026-03-31 11:29 ` Zhijian Li (Fujitsu)
2026-04-01 15:56 ` Peter Xu
2026-04-03 6:15 ` Zhang, GuoQing (Sam)
2026-04-03 9:39 ` Zhijian Li (Fujitsu)
2026-04-03 9:59 ` Zhang, GuoQing (Sam)
2026-04-07 6:15 ` Zhijian Li (Fujitsu)
2026-03-31 11:06 ` Markus Armbruster [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=875x6ctg02.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=Emily.Deng@amd.com \
--cc=PengJu.Zhou@amd.com \
--cc=Qing.Ma@amd.com \
--cc=Victor.Zhao@amd.com \
--cc=eblake@redhat.com \
--cc=farosas@suse.de \
--cc=guoqing.zhang@amd.com \
--cc=lizhijian@fujitsu.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.