qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Leonardo Bras <leobras@redhat.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Juan Quintela" <quintela@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH v3 1/3] QIOChannelSocket: Fix zero-copy flush returning code 1 when nothing sent
Date: Thu, 7 Jul 2022 13:46:53 -0400	[thread overview]
Message-ID: <YsccDel9oiTPqvHW@xz-m1.local> (raw)
In-Reply-To: <20220704202315.507145-2-leobras@redhat.com>

Hi, Leo,

On Mon, Jul 04, 2022 at 05:23:13PM -0300, Leonardo Bras wrote:
> If flush is called when no buffer was sent with MSG_ZEROCOPY, it currently
> returns 1. This return code should be used only when Linux fails to use
> MSG_ZEROCOPY on a lot of sendmsg().
> 
> Fix this by returning early from flush if no sendmsg(...,MSG_ZEROCOPY)
> was attempted.
> 
> Fixes: 2bc58ffc2926 ("QIOChannelSocket: Implement io_writev zero copy flag & io_flush for CONFIG_LINUX")
> Signed-off-by: Leonardo Bras <leobras@redhat.com>
> ---
>  io/channel-socket.c | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/io/channel-socket.c b/io/channel-socket.c
> index 4466bb1cd4..698c086b70 100644
> --- a/io/channel-socket.c
> +++ b/io/channel-socket.c
> @@ -716,12 +716,18 @@ static int qio_channel_socket_flush(QIOChannel *ioc,
>      struct cmsghdr *cm;
>      char control[CMSG_SPACE(sizeof(*serr))];
>      int received;
> -    int ret = 1;
> +    int ret;
> +
> +    if (!sioc->zero_copy_queued) {

I think I asked this in the downstream review but didn't get a
response.. shouldn't this check be "queued == sent"?

> +        return 0;
> +    }
>  
>      msg.msg_control = control;
>      msg.msg_controllen = sizeof(control);
>      memset(control, 0, sizeof(control));
>  
> +    ret = 1;
> +
>      while (sioc->zero_copy_sent < sioc->zero_copy_queued) {
>          received = recvmsg(sioc->fd, &msg, MSG_ERRQUEUE);
>          if (received < 0) {
> -- 
> 2.36.1
> 

-- 
Peter Xu



  parent reply	other threads:[~2022-07-07 17:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 20:23 [PATCH v3 0/3] Zero copy improvements (QIOChannel + multifd) Leonardo Bras
2022-07-04 20:23 ` [PATCH v3 1/3] QIOChannelSocket: Fix zero-copy flush returning code 1 when nothing sent Leonardo Bras
2022-07-05  8:04   ` Daniel P. Berrangé
2022-07-05 15:15     ` Juan Quintela
2022-07-07 17:46   ` Peter Xu [this message]
2022-07-07 19:44     ` Leonardo Bras Soares Passos
2022-07-07 19:52       ` Peter Xu
2022-07-07 21:14         ` Leonardo Brás
2022-07-07 22:18           ` Peter Xu
2022-07-11 19:29             ` Leonardo Bras Soares Passos
2022-07-04 20:23 ` [PATCH v3 2/3] Add dirty-sync-missed-zero-copy migration stat Leonardo Bras
2022-07-05  4:14   ` Markus Armbruster
2022-07-05  8:05   ` Daniel P. Berrangé
2022-07-07 17:54   ` Peter Xu
2022-07-07 19:50     ` Leonardo Bras Soares Passos
2022-07-07 19:56       ` Peter Xu
2022-07-07 21:16         ` Leonardo Brás
2022-07-04 20:23 ` [PATCH v3 3/3] migration/multifd: Warn user when zerocopy not working Leonardo Bras
2022-07-05  8:05   ` Daniel P. Berrangé
2022-07-07 17:56   ` Peter Xu
2022-07-07 19:59     ` Leonardo Bras Soares Passos
2022-07-07 20:06       ` Peter Xu
2022-07-07 21:18         ` Leonardo Brás

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=YsccDel9oiTPqvHW@xz-m1.local \
    --to=peterx@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=leobras@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).