From: Peter Xu <peterx@redhat.com>
To: Bin Guo <guobin@linux.alibaba.com>
Cc: qemu-devel@nongnu.org, lizhijian@fujitsu.com, farosas@suse.de,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH v2 1/2] migration/rdma: honor blocking mode in QIOChannelRDMA readv
Date: Wed, 17 Jun 2026 10:31:02 -0400 [thread overview]
Message-ID: <ajKvputk1JI0tPAY@x1.local> (raw)
In-Reply-To: <20260617064332.75618-1-guobin@linux.alibaba.com>
On Wed, Jun 17, 2026 at 02:43:31PM +0800, Bin Guo wrote:
> QIOChannelRDMA's readv already blocks inside qemu_rdma_exchange_recv()
> when waiting for the next RDMA SEND message. What it did not do was
> keep blocking when the bytes from a single receive were insufficient
> to satisfy the full request -- it returned partial data (or EAGAIN)
> instead of waiting for more.
Sorry if I wasn't clear when commenting, but what I meant is, this is
correct behavior for blocking/nonblocking.
If io_readv() reads partial, IIUC returning how much it reads is the
correct behavior. You can refer to qio_channel_socket_readv().
Here, RDMA doesn't respect blocking is because it _always_ blocks. That
is, qemu_rdma_exchange_recv() always will block even if blocking=false.
I believe it will normally stop working when it's used in a coroutine,
because normally we rely on non-blocking to allow it fallback to caller
then things like qio_channel_wait_cond() will yield if it's coroutine.
I recall RDMA still works only because it has some internal hack to yield,
maybe that's qemu_rdma_wait_comp_channel(), but I really don't know RDMA
well, at least so far.. maybe I should try to improve at some point.
Before that, it would be good Zhijian can have another look on this.
Let me loop in Dan too.
Thanks,
>
> Loop on qemu_rdma_exchange_recv() when the channel is blocking and
> the receive buffer cannot satisfy the request. This matches the
> behaviour of other QIOChannel implementations, which block until
> the full request is satisfied (or an error occurs).
>
> Also remove the stale XXX comments about unimplemented blocking support.
>
> Reviewed-by: Li Zhijian <lizhijian@fujitsu.com>
> Signed-off-by: Bin Guo <guobin@linux.alibaba.com>
> ---
> migration/rdma.c | 46 +++++++++++++++++++++-------------------------
> 1 file changed, 21 insertions(+), 25 deletions(-)
>
> diff --git a/migration/rdma.c b/migration/rdma.c
> index 3e37a1d440..201cb9eb12 100644
> --- a/migration/rdma.c
> +++ b/migration/rdma.c
> @@ -388,7 +388,7 @@ struct QIOChannelRDMA {
> QIOChannel parent;
> RDMAContext *rdmain;
> RDMAContext *rdmaout;
> - bool blocking; /* XXX we don't actually honour this yet */
> + bool blocking;
> };
>
> /*
> @@ -2710,32 +2710,29 @@ static ssize_t qio_channel_rdma_readv(QIOChannel *ioc,
> break;
> }
>
> -
> - /* We've got nothing at all, so lets wait for
> - * more to arrive
> - */
> - ret = qemu_rdma_exchange_recv(rdma, &head, RDMA_CONTROL_QEMU_FILE,
> - errp);
> -
> - if (ret < 0) {
> - rdma->errored = true;
> - return -1;
> - }
> -
> /*
> - * SEND was received with new bytes, now try again.
> + * We've got nothing at all, so lets wait for
> + * more to arrive.
> */
> - len = qemu_rdma_fill(rdma, data, want, 0);
> - done += len;
> - want -= len;
> -
> - /* Still didn't get enough, so lets just return */
> - if (want) {
> - if (done == 0) {
> - return QIO_CHANNEL_ERR_BLOCK;
> - } else {
> - break;
> + do {
> + ret = qemu_rdma_exchange_recv(rdma, &head,
> + RDMA_CONTROL_QEMU_FILE, errp);
> + if (ret < 0) {
> + rdma->errored = true;
> + return -1;
> }
> +
> + /*
> + * SEND was received with new bytes, now try again.
> + */
> + len = qemu_rdma_fill(rdma, data, want, 0);
> + done += len;
> + want -= len;
> + data += len;
> + } while (want && rioc->blocking);
> +
> + if (want && done == 0) {
> + return QIO_CHANNEL_ERR_BLOCK;
> }
> }
> return done;
> @@ -2771,7 +2768,6 @@ static int qio_channel_rdma_set_blocking(QIOChannel *ioc,
> Error **errp)
> {
> QIOChannelRDMA *rioc = QIO_CHANNEL_RDMA(ioc);
> - /* XXX we should make readv/writev actually honour this :-) */
> rioc->blocking = blocking;
> return 0;
> }
> --
> 2.50.1 (Apple Git-155)
>
--
Peter Xu
next prev parent reply other threads:[~2026-06-17 14:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 6:43 [PATCH v2 1/2] migration/rdma: honor blocking mode in QIOChannelRDMA readv Bin Guo
2026-06-17 6:43 ` [PATCH v2 2/2] migration/rdma: account transferred bytes for zero page compression Bin Guo
2026-06-17 14:31 ` Peter Xu [this message]
2026-06-18 5:55 ` [PATCH v2 1/2] migration/rdma: honor blocking mode in QIOChannelRDMA readv laiqi.gb via qemu development
-- strict thread matches above, loose matches on Subject: below --
2026-05-29 7:04 [PATCH 0/2] migration/rdma: fix blocking readv and zero-page accounting Bin Guo
2026-05-29 7:04 ` [PATCH 1/2] migration/rdma: honor blocking mode in QIOChannelRDMA readv Bin Guo
2026-06-16 19:09 ` Peter Xu
2026-06-17 6:36 ` Bin Guo
2026-06-17 7:27 ` laiqi.gb via qemu development
2026-05-29 7:04 ` [PATCH 2/2] migration/rdma: account transferred bytes for zero page compression Bin Guo
2026-06-08 1:51 ` [PATCH 0/2] migration/rdma: fix blocking readv and zero-page accounting Zhijian Li (Fujitsu)
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=ajKvputk1JI0tPAY@x1.local \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=guobin@linux.alibaba.com \
--cc=lizhijian@fujitsu.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.