From: Ivan Ren <renyime@gmail.com>
To: quintela@redhat.com, dgilbert@redhat.com
Cc: richardw.yang@linux.intel.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v3 3/3] migration: update ram_counters for multifd sync packet
Date: Tue, 30 Jul 2019 13:33:36 +0800 [thread overview]
Message-ID: <1564464816-21804-4-git-send-email-ivanren@tencent.com> (raw)
In-Reply-To: <1564464816-21804-1-git-send-email-ivanren@tencent.com>
From: Ivan Ren <ivanren@tencent.com>
Multifd sync will send MULTIFD_FLAG_SYNC flag info to destination, add
these bytes to ram_counters record.
Signed-off-by: Ivan Ren <ivanren@tencent.com>
Suggested-by: Wei Yang <richardw.yang@linux.intel.com>
---
migration/ram.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/migration/ram.c b/migration/ram.c
index 88ddd2bbe2..20b6eebb7c 100644
--- a/migration/ram.c
+++ b/migration/ram.c
@@ -1085,6 +1085,8 @@ static void multifd_send_sync_main(RAMState *rs)
p->flags |= MULTIFD_FLAG_SYNC;
p->pending_job++;
qemu_file_update_transfer(rs->f, p->packet_len);
+ ram_counters.multifd_bytes += p->packet_len;
+ ram_counters.transferred += p->packet_len;
qemu_mutex_unlock(&p->mutex);
qemu_sem_post(&p->sem);
}
--
2.17.2 (Apple Git-113)
next prev parent reply other threads:[~2019-07-30 5:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 5:33 [Qemu-devel] [PATCH v2 0/3] migration: add speed limit for multifd migration Ivan Ren
2019-07-30 5:33 ` [Qemu-devel] [PATCH v3 1/3] migration: add qemu_file_update_transfer interface Ivan Ren
2019-08-07 8:45 ` Juan Quintela
2019-07-30 5:33 ` [Qemu-devel] [PATCH v3 2/3] migration: add speed limit for multifd migration Ivan Ren
2019-07-31 0:26 ` Wei Yang
2019-08-07 8:46 ` Juan Quintela
2019-07-30 5:33 ` Ivan Ren [this message]
2019-08-07 8:46 ` [Qemu-devel] [PATCH v3 3/3] migration: update ram_counters for multifd sync packet Juan Quintela
2019-08-07 18:53 ` [Qemu-devel] [PATCH v2 0/3] migration: add speed limit for multifd migration Dr. David Alan Gilbert
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=1564464816-21804-4-git-send-email-ivanren@tencent.com \
--to=renyime@gmail.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=richardw.yang@linux.intel.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).