qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: mrhines@linux.vnet.ibm.com
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com, mst@redhat.com, quintela@redhat.com,
	owasserm@redhat.com, abali@us.ibm.com, mrhines@us.ibm.com,
	gokul@us.ibm.com, pbonzini@redhat.com
Subject: [Qemu-devel] [PULL v4 10/11] rdma: print out throughput while debugging
Date: Wed, 17 Apr 2013 19:07:19 -0400	[thread overview]
Message-ID: <1366240040-10730-11-git-send-email-mrhines@linux.vnet.ibm.com> (raw)
In-Reply-To: <1366240040-10730-1-git-send-email-mrhines@linux.vnet.ibm.com>

From: "Michael R. Hines" <mrhines@us.ibm.com>

It's very helpful when debugging to print out migration throughput
after each iteration round to compare the different migration
technologies.

Signed-off-by: Michael R. Hines <mrhines@us.ibm.com>
---
 migration.c |    8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/migration.c b/migration.c
index 2f33914..6dac831 100644
--- a/migration.c
+++ b/migration.c
@@ -35,6 +35,9 @@
     do { } while (0)
 #endif
 
+#define MBPS(bytes, time) (time ? ((((double) bytes * 8)         \
+        / ((double) time / 1000.0)) / 1000.0 / 1000.0) : -1.0)
+
 enum {
     MIG_STATE_ERROR,
     MIG_STATE_SETUP,
@@ -564,8 +567,9 @@ static void *migration_thread(void *opaque)
             max_size = bandwidth * migrate_max_downtime() / 1000000;
 
             DPRINTF("transferred %" PRIu64 " time_spent %" PRIu64
-                    " bandwidth %g max_size %" PRId64 "\n",
-                    transferred_bytes, time_spent, bandwidth, max_size);
+                    " bandwidth %g throughput %f max_size %" PRId64 "\n",
+                    transferred_bytes, time_spent, bandwidth,
+                    MBPS(transferred_bytes, time_spent), max_size);
             /* if we haven't sent anything, we don't want to recalculate
                10000 is a small enough number for our purposes */
             if (s->dirty_bytes_rate && transferred_bytes > 10000) {
-- 
1.7.10.4

  parent reply	other threads:[~2013-04-17 23:07 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17 23:07 [Qemu-devel] [PULL v4 00/11] rdma: migration support mrhines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 01/11] rdma: export yield_until_fd_readable() mrhines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 02/11] rdma: introduce qemu_ram_foreach_block() mrhines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 03/11] rdma: introduce qemu_file_mode_is_not_valid() mrhines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 04/11] rdma: export ram_handle_compressed() mrhines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 05/11] rdma: export qemu_fflush() mrhines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 06/11] rdma: new QEMUFileOps hooks mrhines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 07/11] rdma: introduce capability for chunk registration mrhines
2013-04-18 22:07   ` Eric Blake
2013-04-19  0:34     ` Michael R. Hines
2013-04-20 17:02     ` Michael S. Tsirkin
2013-04-21 13:19       ` Paolo Bonzini
2013-04-21 14:17         ` Michael S. Tsirkin
2013-04-21 17:19           ` Michael R. Hines
2013-04-21 19:13             ` Michael S. Tsirkin
2013-04-21 16:05         ` Michael R. Hines
2013-04-21 18:59           ` Michael S. Tsirkin
2013-04-21 19:55             ` Michael R. Hines
2013-04-21 16:06         ` Michael R. Hines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 08/11] rdma: core logic mrhines
2013-04-18  7:55   ` Paolo Bonzini
2013-04-18 13:57     ` Michael R. Hines
2013-04-18  7:58   ` Michael S. Tsirkin
2013-04-18 13:59     ` Michael R. Hines
2013-04-18 13:06       ` Michael S. Tsirkin
2013-04-18 14:14         ` Michael R. Hines
2013-04-18 13:32           ` Michael S. Tsirkin
2013-04-18 14:45             ` Michael R. Hines
2013-04-18 13:52               ` Michael S. Tsirkin
2013-04-18 15:14                 ` Anthony Liguori
2013-04-18 14:53             ` [Qemu-devel] licensing of IBM contributions to QEMU (was Re: [PULL v4 08/11] rdma: core logic) Paolo Bonzini
2013-04-18 19:15               ` Michael R. Hines
2013-04-19  0:35               ` Anthony Liguori
2013-04-18  8:44   ` [Qemu-devel] [PULL v4 08/11] rdma: core logic Orit Wasserman
2013-04-18 13:54     ` Michael R. Hines
2013-04-18 15:51       ` Orit Wasserman
2013-04-18 19:41         ` Michael R. Hines
2013-04-18 22:12   ` Eric Blake
2013-04-19  0:35     ` Michael R. Hines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 09/11] rdma: send pc.ram mrhines
2013-04-17 23:07 ` mrhines [this message]
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 11/11] rdma: add documentation mrhines
2013-04-18  6:55   ` Michael S. Tsirkin
2013-04-19  0:57     ` Michael R. Hines
2013-04-17 23:39 ` [Qemu-devel] [PULL v4 00/11] rdma: migration support Anthony Liguori
2013-04-18 13:46   ` Michael R. Hines
2013-04-18  7:00 ` Michael S. Tsirkin
2013-04-18 13:49   ` Michael R. Hines
2013-04-18 13:50     ` Michael S. Tsirkin
2013-04-18 19:17       ` Michael R. Hines
2013-04-18 20:12         ` Michael S. Tsirkin
2013-04-18 21:28           ` Michael R. Hines
2013-04-18 20:33             ` Michael S. Tsirkin
2013-04-18 14:36   ` Michael R. Hines

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=1366240040-10730-11-git-send-email-mrhines@linux.vnet.ibm.com \
    --to=mrhines@linux.vnet.ibm.com \
    --cc=abali@us.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=gokul@us.ibm.com \
    --cc=mrhines@us.ibm.com \
    --cc=mst@redhat.com \
    --cc=owasserm@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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 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).