From: Peter Xu <peterx@redhat.com>
To: Hao Xiang <hao.xiang@bytedance.com>
Cc: qemu-devel@nongnu.org, farosas@suse.de
Subject: Re: [External] Re: [PATCH 0/6] Introduce multifd zero page checking.
Date: Thu, 8 Feb 2024 10:36:43 +0800 [thread overview]
Message-ID: <ZcQ-O8tp_Bo0API_@x1n> (raw)
In-Reply-To: <CAAYibXjQYkpL+L8pLX5DQ4hTWqFAc2pcpkJFmE5bs=O5vzhDPg@mail.gmail.com>
On Wed, Feb 07, 2024 at 04:47:27PM -0800, Hao Xiang wrote:
> Sure I will drop "throughput" to avoid confusion. In my testing, 1
> multifd channel already makes the main thread spin at 100%. So the
> total-time is the same across 1/2/4 multifd channels as long as zero
> page is run on the main migration thread. Of course, this is based on
> the fact that the network is not the bottleneck. One interesting
> finding is that multifd 1 channel with multifd zero page has better
> performance than multifd 1 channel with main migration thread.
It's probably because the main thread has even more works to do than
"detecting zero page" alone.
When zero detection is done in main thread and when the guest is fully
idle, it'll consume a major portion of main thread cpu resource scanning
those pages already. Consider all pages zero, multifd threads should be
fully idle, so n_channels may not matter here.
When 1 multifd thread created with zero-page offloading, zero page is fully
offloaded from main -> multifd thread even if only one. It's kind of a
similar effect of forking the main thread into two threads, so the main
thread can be more efficient on other tasks (fetching/scanning dirty bits,
etc.).
Thanks,
--
Peter Xu
prev parent reply other threads:[~2024-02-08 2:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 23:19 [PATCH 0/6] Introduce multifd zero page checking Hao Xiang
2024-02-06 23:19 ` [PATCH 1/6] migration/multifd: Add new migration option multifd-zero-page Hao Xiang
2024-02-07 3:44 ` Peter Xu
2024-02-08 0:49 ` [External] " Hao Xiang
2024-02-06 23:19 ` [PATCH 2/6] migration/multifd: Add zero pages and zero bytes counter to migration status interface Hao Xiang
2024-02-07 4:13 ` Peter Xu
2024-02-07 4:37 ` Peter Xu
2024-02-07 8:41 ` Jiri Denemark
2024-02-07 23:44 ` [External] " Hao Xiang
2024-02-08 2:51 ` Peter Xu
2024-02-06 23:19 ` [PATCH 3/6] migration/multifd: Support for zero pages transmission in multifd format Hao Xiang
2024-02-07 4:25 ` Peter Xu
2024-02-08 19:03 ` [External] " Hao Xiang
2024-02-06 23:19 ` [PATCH 4/6] migration/multifd: Zero page transmission on the multifd thread Hao Xiang
2024-02-07 4:45 ` Peter Xu
2024-02-06 23:19 ` [PATCH 5/6] migration/multifd: Enable zero page checking from multifd threads Hao Xiang
2024-02-06 23:19 ` [PATCH 6/6] migration/multifd: Add a new migration test case for legacy zero page checking Hao Xiang
2024-02-07 3:39 ` [PATCH 0/6] Introduce multifd " Peter Xu
2024-02-08 0:47 ` [External] " Hao Xiang
2024-02-08 2:36 ` Peter Xu [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=ZcQ-O8tp_Bo0API_@x1n \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=hao.xiang@bytedance.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 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).