From: Juan Quintela <quintela@redhat.com>
To: Zhenzhong Duan <zhenzhong.duan@intel.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com
Subject: Re: [PATCH 2/2] multifd: Fix flush of zero copy page send request
Date: Thu, 02 Feb 2023 21:14:46 +0100 [thread overview]
Message-ID: <87wn4zsu2x.fsf@secure.mitica> (raw)
In-Reply-To: <20221017075351.2974642-2-zhenzhong.duan@intel.com> (Zhenzhong Duan's message of "Mon, 17 Oct 2022 15:53:51 +0800")
Zhenzhong Duan <zhenzhong.duan@intel.com> wrote:
> Make IO channel flush call after the inflight request has been drained
> in multifd thread, or else we may missed to flush the inflight request.
>
> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
Good catch!!!!!
Reviewed-by: Juan Quintela <quintela@redhat.com>
queued the whole series.
next prev parent reply other threads:[~2023-02-02 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 7:53 [PATCH 1/2] multifd: Fix a race on reading MultiFDPages_t.block Zhenzhong Duan
2022-10-17 7:53 ` [PATCH 2/2] multifd: Fix flush of zero copy page send request Zhenzhong Duan
2023-02-02 20:14 ` Juan Quintela [this message]
2023-02-02 20:13 ` [PATCH 1/2] multifd: Fix a race on reading MultiFDPages_t.block Juan Quintela
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=87wn4zsu2x.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhenzhong.duan@intel.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).