From: Markus Armbruster <armbru@redhat.com>
To: Hao Xiang <hao.xiang@bytedance.com>
Cc: pbonzini@redhat.com, berrange@redhat.com, eduardo@habkost.net,
peterx@redhat.com, farosas@suse.de, eblake@redhat.com,
thuth@redhat.com, lvivier@redhat.com, jdenemar@redhat.com,
marcel.apfelbaum@gmail.com, philmd@linaro.org,
wangyanan55@huawei.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v3 6/7] migration/multifd: Add zero pages and zero bytes counter to migration status interface.
Date: Wed, 28 Feb 2024 10:52:12 +0100 [thread overview]
Message-ID: <87wmqozzjn.fsf@pond.sub.org> (raw)
In-Reply-To: <20240226195654.934709-7-hao.xiang@bytedance.com> (Hao Xiang's message of "Mon, 26 Feb 2024 19:56:53 +0000")
Hao Xiang <hao.xiang@bytedance.com> writes:
> This change extends the MigrationStatus interface to track zero pages
> and zero bytes counter.
>
> Signed-off-by: Hao Xiang <hao.xiang@bytedance.com>
[...]
> diff --git a/qapi/migration.json b/qapi/migration.json
> index a0a85a0312..171734c07e 100644
> --- a/qapi/migration.json
> +++ b/qapi/migration.json
> @@ -63,6 +63,10 @@
> # between 0 and @dirty-sync-count * @multifd-channels. (since
> # 7.1)
> #
> +# @zero-pages: number of zero pages (since 9.0)
> +#
> +# @zero-bytes: number of zero bytes sent (since 9.0)
> +#
Awfully terse. How are these two related?
> # Features:
> #
> # @deprecated: Member @skipped is always zero since 1.5.3
[...]
next prev parent reply other threads:[~2024-02-28 9:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 19:56 [PATCH v3 0/7] Introduce multifd zero page checking Hao Xiang
2024-02-26 19:56 ` [PATCH v3 1/7] migration/multifd: Add new migration option zero-page-detection Hao Xiang
2024-02-28 9:43 ` Markus Armbruster
2024-02-28 18:30 ` [External] " Hao Xiang
2024-02-29 5:34 ` Markus Armbruster
2024-02-26 19:56 ` [PATCH v3 2/7] migration/multifd: Implement zero page transmission on the multifd thread Hao Xiang
2024-02-28 9:45 ` Markus Armbruster
2024-02-28 9:50 ` Markus Armbruster
2024-02-28 18:45 ` [External] " Hao Xiang
2024-02-29 5:41 ` Markus Armbruster
2024-02-29 15:46 ` Fabiano Rosas
2024-03-01 1:27 ` Hao Xiang
2024-02-28 19:46 ` Fabiano Rosas
2024-03-01 1:55 ` [External] " Hao Xiang
2024-02-26 19:56 ` [PATCH v3 3/7] migration/multifd: Implement ram_save_target_page_multifd to handle multifd version of MigrationOps::ram_save_target_page Hao Xiang
2024-02-28 19:48 ` Fabiano Rosas
2024-02-26 19:56 ` [PATCH v3 4/7] migration/multifd: Enable multifd zero page checking by default Hao Xiang
2024-02-26 19:56 ` [PATCH v3 5/7] migration/multifd: Add new migration test cases for legacy zero page checking Hao Xiang
2024-02-26 19:56 ` [PATCH v3 6/7] migration/multifd: Add zero pages and zero bytes counter to migration status interface Hao Xiang
2024-02-28 9:52 ` Markus Armbruster [this message]
2024-02-28 18:36 ` [External] " Hao Xiang
2024-02-29 6:01 ` Markus Armbruster
2024-03-01 1:18 ` Hao Xiang
2024-03-01 5:53 ` Markus Armbruster
2024-02-26 19:56 ` [PATCH v3 7/7] Update maintainer contact for migration multifd zero page checking acceleration Hao Xiang
2024-02-28 9:36 ` [PATCH v3 0/7] Introduce multifd zero page checking Markus Armbruster
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=87wmqozzjn.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=farosas@suse.de \
--cc=hao.xiang@bytedance.com \
--cc=jdenemar@redhat.com \
--cc=lvivier@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wangyanan55@huawei.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 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.