From: Peter Xu <peterx@redhat.com>
To: Hao Xiang <hao.xiang@bytedance.com>
Cc: qemu-devel@nongnu.org, farosas@suse.de,
Jiri Denemark <jdenemar@redhat.com>
Subject: Re: [PATCH 2/6] migration/multifd: Add zero pages and zero bytes counter to migration status interface.
Date: Wed, 7 Feb 2024 12:37:15 +0800 [thread overview]
Message-ID: <ZcMI-wPq94x6cO2Z@x1n> (raw)
In-Reply-To: <ZcMDVpLilA-PZ3he@x1n>
On Wed, Feb 07, 2024 at 12:13:10PM +0800, Peter Xu wrote:
> On Tue, Feb 06, 2024 at 11:19:04PM +0000, Hao Xiang wrote:
> > This change extends the MigrationStatus interface to track zero pages
> > and zero bytes counter.
> >
> > Signed-off-by: Hao Xiang <hao.xiang@bytedance.com>
>
> Reviewed-by: Peter Xu <peterx@redhat.com>
I'll need to scratch this, sorry..
The issue is I forgot we have "duplicate" which is exactly "zero
page"s.. See:
info->ram->duplicate = stat64_get(&mig_stats.zero_pages);
If you think the name too confusing and want a replacement, maybe it's fine
and maybe we can do that. Then we can keep this zero page counter
introduced, reporting the same value as duplicates, then with a follow up
patch to deprecate "duplicate" parameter. See an exmaple on how to
deprecate in 7b24d326348e1672.
One thing I'm not sure is whether Libvirt will be fine on losing
"duplicates" after 2+ QEMU major releases. Copy Jiri for this. My
understanding is that Libvirt should be keeping an eye on deprecation list
and react, but I'd like to double check..
Or we can keep using "duplicates", but I agree it just reads weird..
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2024-02-07 4: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 [this message]
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
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=ZcMI-wPq94x6cO2Z@x1n \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=hao.xiang@bytedance.com \
--cc=jdenemar@redhat.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 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.