From: "Dr. David Alan Gilbert" <dave@treblig.org>
To: Peter Xu <peterx@redhat.com>
Cc: "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Fabiano Rosas <farosas@suse.de>,
Prasad Pandit <ppandit@redhat.com>,
Juraj Marcin <jmarcin@redhat.com>
Subject: Re: [PATCH v2 2/2] migration/hmp: Add "info migrate -a", reorg the dump
Date: Wed, 21 May 2025 21:04:58 +0000 [thread overview]
Message-ID: <aC4_-nMc7FwsMf9p@gallifrey> (raw)
In-Reply-To: <aC3dJvwXK9eW1YO6@x1.local>
* Peter Xu (peterx@redhat.com) wrote:
> On Wed, May 21, 2025 at 08:43:37AM +0000, Zhijian Li (Fujitsu) wrote:
> [...]
> > > After this change, sample output (default, no "-a" specified):
> > >
> > > Status: postcopy-active
> > > Time (ms): total=40504, setup=14, down=145
> > > RAM info:
> > > Bandwidth (mbps): 6102.65
> > > Sizes (KB): psize=4, total=16777992
> > > transferred=37673019, remain=2136404,
> > > precopy=3, multifd=26108780, postcopy=11563855
> > > Pages: normal=9394288, zero=600672, rate_per_sec=185875
> > > Others: dirty_syncs=3, dirty_pages_rate=278378, postcopy_req=4078
> >
> > (Feel free to ignore my comment if you have reached a consensus.)
> >
> > Putting multiple fields in one line is a true need for human reading?
>
> It definitely helps me but I agree that can be subjective. So I'm happy to
> collect opinions.
>
> So my above layout was trying to leverage more on screens where width is
> bigger than the height (which is pretty much the default).
I think perhaps the problem with the on-one-line layout is that the grouping
is wrong; grouping by unit probably doesn't make sense.
So it makes sense to me to have:
Sizes: psize=4/KB
Transfer: total=16777992 kB transferred=37673019 kB remain=11563855 kB
Pages: normal=9394288 zero=600672
Page rates: transferred=185875/s dirtied=278378/s
Other: dirty_sync=3 postcopy_req=4078
so you have things on one line when you're comparing them - so it's easy
to see the transferred page/s is way less than the dirtied in this example
(really??) because they're next to each other.
Or the 'Transfer' line is showing total, how much so far and how much remains
> > I don't have confident to reorg them so I feed this request to the AI,
> > he suggested something like this:
> >
> > Migration Status:
> > Status: completed
> >
> > Time Statistics:
> > Setup: 15 ms
> > Downtime: 76 ms
> > Total: 122952 ms
> > RAM Transfer:
> > Throughput: 8717.68 mbps
> > Page Size: 4 KB
> > Transferred:
> > Total: 130825923 KB
> > Precopied: 15 KB
> > Postcopied: 13691151 KB
> > Multifd: 117134260 KB
> > Remaining: 0 KB
> > Total RAM: 16777992 KB
> > Page Statistics:
> > Normal Pages: 32622225
> > Zero Pages: 0
> > Duplicate Pages: 997263
> > Transfer Page Rate: 169431
> > Dirty Page Rate: 1234
> > Dirty Syncs: 10
>
> I would trust you more than the AI, so feel free to share your opinion next
> time (which won't hurt if it was a result of AI discussions, but only which
> you agreed on :).
Haha, yes; whatever it is for those humans find easiest - that's the H in HMP!
(Those AIs can parse Json way easier than I can read Json!)
Of course you don't need to reorg it all at once again, if someone finds
one section hard, then reorg the way that people find it easy.
> It's already in a pull, let's revisit whenever necessary. Thanks for the
> input!
>
Nod.
Dave
> --
> Peter Xu
>
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2025-05-21 21:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 20:01 [PATCH v2 0/2] migration: Some fix and enhancements to HMP "info migrate" Peter Xu
2025-05-14 20:01 ` [PATCH v2 1/2] migration: Allow caps to be set when preempt or multifd cap enabled Peter Xu
2025-05-22 20:15 ` Michael Tokarev
2025-05-14 20:01 ` [PATCH v2 2/2] migration/hmp: Add "info migrate -a", reorg the dump Peter Xu
2025-05-14 20:29 ` Dr. David Alan Gilbert
2025-05-14 21:17 ` Peter Xu
2025-05-14 23:00 ` Dr. David Alan Gilbert
2025-05-21 8:43 ` Zhijian Li (Fujitsu) via
2025-05-21 14:03 ` Peter Xu
2025-05-21 21:04 ` Dr. David Alan Gilbert [this message]
2025-05-22 0:55 ` Zhijian Li (Fujitsu) via
2025-05-22 13:16 ` Peter Xu
2025-05-23 2:06 ` Zhijian Li (Fujitsu) via
2025-05-26 15:40 ` Peter Xu
2025-05-22 1:07 ` Zhijian Li (Fujitsu) via
2025-05-19 11:27 ` [PATCH v2 0/2] migration: Some fix and enhancements to HMP "info migrate" Mario Casquero
2025-05-20 17:03 ` 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=aC4_-nMc7FwsMf9p@gallifrey \
--to=dave@treblig.org \
--cc=farosas@suse.de \
--cc=jmarcin@redhat.com \
--cc=lizhijian@fujitsu.com \
--cc=peterx@redhat.com \
--cc=ppandit@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 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).