qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>,
	Leonardo Bras <leobras@redhat.com>, Peter Xu <peterx@redhat.com>
Subject: [PATCH 1/2] migration: Document all migration_stats
Date: Thu,  4 May 2023 12:33:56 +0200	[thread overview]
Message-ID: <20230504103357.22130-2-quintela@redhat.com> (raw)
In-Reply-To: <20230504103357.22130-1-quintela@redhat.com>

Signed-off-by: Juan Quintela <quintela@redhat.com>
---
 migration/migration-stats.h | 43 +++++++++++++++++++++++++++++++++++++
 1 file changed, 43 insertions(+)

diff --git a/migration/migration-stats.h b/migration/migration-stats.h
index 149af932d7..0e49c236fa 100644
--- a/migration/migration-stats.h
+++ b/migration/migration-stats.h
@@ -22,17 +22,60 @@
  * one thread).
  */
 typedef struct {
+    /*
+     * number of bytes that were dirty last time that we sync with the
+     * guest memory.  We use that to calculate the downtime.  As the
+     * remaining dirty amounts to what we know that is still dirty
+     * since last iteration, not counting what the guest has dirtied
+     * sync we synchronize bitmaps.
+     */
     Stat64 dirty_bytes_last_sync;
+    /*
+     * number of pages dirtied by second.
+     */
     Stat64 dirty_pages_rate;
+    /*
+     * number of times we have synchronize guest bitmaps.
+     */
     Stat64 dirty_sync_count;
+    /*
+     * number of times zero copy failed to send any page using zero
+     * copy.
+     */
     Stat64 dirty_sync_missed_zero_copy;
+    /*
+     * number of bytes sent at migration completion stage while the
+     * guest is stopped.
+     */
     Stat64 downtime_bytes;
+    /*
+     * number of pages transferred that were full of zeros.
+     */
     Stat64 zero_pages;
+    /*
+     * number of bytes sent through multifd channels.
+     */
     Stat64 multifd_bytes;
+    /*
+     * number of pages transferred that were not full of zeros.
+     */
     Stat64 normal_pages;
+    /*
+     * number of bytes sent during postcopy.
+     */
     Stat64 postcopy_bytes;
+    /*
+     * number of postcopy page faults that we have handled during
+     * postocpy stage.
+     */
     Stat64 postcopy_requests;
+    /*
+     *  number of bytes sent during precopy stage.
+     */
     Stat64 precopy_bytes;
+    /*
+     * total number of bytes transferred.
+     */
     Stat64 transferred;
 } MigrationAtomicStats;
 
-- 
2.40.0



  reply	other threads:[~2023-05-04 10:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 10:33 [PATCH 0/2] More migration stats Juan Quintela
2023-05-04 10:33 ` Juan Quintela [this message]
2023-05-04 12:37   ` [PATCH 1/2] migration: Document all migration_stats David Edmondson
2023-05-04 17:38     ` Juan Quintela
2023-05-04 16:47   ` Daniel P. Berrangé
2023-05-04 17:39     ` Juan Quintela
2023-05-04 10:33 ` [PATCH 2/2] migration: Put zero_pages in alphabetical order Juan Quintela
2023-05-04 12:38   ` David Edmondson
2023-05-04 16:47   ` Daniel P. Berrangé
2023-05-25 15:06   ` 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=20230504103357.22130-2-quintela@redhat.com \
    --to=quintela@redhat.com \
    --cc=leobras@redhat.com \
    --cc=peterx@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).