From: Peter Xu <peterx@redhat.com>
To: Fabiano Rosas <farosas@suse.de>, Yuan Liu <yuan1.liu@intel.com>
Cc: Yuan Liu <yuan1.liu@intel.com>,
qemu-devel@nongnu.org, hao.xiang@bytedance.com,
bryan.zhang@bytedance.com, nanhai.zou@intel.com
Subject: Re: [PATCH 1/1] migration/multifd: solve zero page causing multiple page faults
Date: Wed, 3 Apr 2024 15:41:45 -0400 [thread overview]
Message-ID: <Zg2w-a0EQF_8yYHx@x1n> (raw)
In-Reply-To: <874jcjdir6.fsf@suse.de>
On Tue, Apr 02, 2024 at 09:57:49AM -0300, Fabiano Rosas wrote:
> Yuan Liu <yuan1.liu@intel.com> writes:
>
> > Implemented recvbitmap tracking of received pages in multifd.
> >
> > If the zero page appears for the first time in the recvbitmap, this
> > page is not checked and set.
> >
> > If the zero page has already appeared in the recvbitmap, there is no
> > need to check the data but directly set the data to 0, because it is
> > unlikely that the zero page will be migrated multiple times.
> >
> > Signed-off-by: Yuan Liu <yuan1.liu@intel.com>
>
> Reviewed-by: Fabiano Rosas <farosas@suse.de>
>
I queued it with below squashed to update the comment. I hope it works for
you. Thanks,
===8<===
diff --git a/include/exec/ramblock.h b/include/exec/ramblock.h
index 848915ea5b..7062da380b 100644
--- a/include/exec/ramblock.h
+++ b/include/exec/ramblock.h
@@ -57,7 +57,7 @@ struct RAMBlock {
off_t bitmap_offset;
uint64_t pages_offset;
- /* bitmap of already received pages in postcopy */
+ /* Bitmap of already received pages. Only used on destination side. */
unsigned long *receivedmap;
/*
===8<===
--
Peter Xu
next prev parent reply other threads:[~2024-04-03 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 15:41 [PATCH 0/1] Solve zero page causing multiple page faults Yuan Liu
2024-04-01 15:41 ` [PATCH 1/1] migration/multifd: solve " Yuan Liu
2024-04-02 12:57 ` Fabiano Rosas
2024-04-03 19:41 ` Peter Xu [this message]
2024-04-02 7:43 ` [PATCH 0/1] Solve " Liu, Yuan1
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=Zg2w-a0EQF_8yYHx@x1n \
--to=peterx@redhat.com \
--cc=bryan.zhang@bytedance.com \
--cc=farosas@suse.de \
--cc=hao.xiang@bytedance.com \
--cc=nanhai.zou@intel.com \
--cc=qemu-devel@nongnu.org \
--cc=yuan1.liu@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).