All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>
Cc: "Dr. David Alan Gilbert" <dave@treblig.org>,
	"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: Thu, 22 May 2025 09:16:03 -0400	[thread overview]
Message-ID: <aC8jkx-PnaJsuUB5@x1.local> (raw)
In-Reply-To: <80ff85f3-1e75-43f9-aeff-99e5033e6090@fujitsu.com>

On Thu, May 22, 2025 at 12:55:05AM +0000, Zhijian Li (Fujitsu) wrote:
> 
> 
> On 22/05/2025 05:04, Dr. David Alan Gilbert wrote:
> > * 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
> 
> 
> Oh, I vote this !!, more clear to me.

I followed up with Dave's idea, but then added all entries into it, below.

  Status: postcopy-active
  Time (ms): total=40504, setup=14, down=145
  RAM info:
    Throughput (Mbps): 6102.65
    Sizes (KiB):        pagesize=4, total=16777992
    Transfers (KiB):    transferred=37673019, remain=2136404
      Channels (KiB):   precopy=3, multifd=26108780, postcopy=11563855
      Page Types:       normal=9394288, zero=600672
    Page Rates (pps):   transfer_rate=185875, dirty_rate=278378
    Others:             dirty_syncs=3, postcopy_req=4078

Logically I should have moved "Throughput" out, because that should also
include all other things (non-ram iterators, device states).  But currently
it's an entry under info->ram.. so I kept it there.

It also has the "total" in "Sizes" to make the next line shorter
(meanwhile, "total" is also a constant size like "psize"), the hope is it's
still close enough to read when reading "Transfers" on the next line.

I also provided further indents to "Channels" and "Page Types" because they
should be taken as sub-class of "Transfer".

How is this?  Since we're at it, I can send a follow up patch after we
reach a consensus (I may also include that in another series where I'll
further add things into HMP; I'm looking at making blocktime to report page
latencies too).

-- 
Peter Xu



  reply	other threads:[~2025-05-22 13:18 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
2025-05-22  0:55         ` Zhijian Li (Fujitsu) via
2025-05-22 13:16           ` Peter Xu [this message]
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=aC8jkx-PnaJsuUB5@x1.local \
    --to=peterx@redhat.com \
    --cc=dave@treblig.org \
    --cc=farosas@suse.de \
    --cc=jmarcin@redhat.com \
    --cc=lizhijian@fujitsu.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 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.