summaryrefslogtreecommitdiff
path: root/migration
diff options
context:
space:
mode:
authorLidong Chen <jemmy858585@gmail.com>2018-03-10 22:32:58 +0800
committerDr. David Alan Gilbert <dgilbert@redhat.com>2018-03-23 16:37:15 +0000
commite8a0f2f9a18f6ab4aa4896cef0010bcad1f323c4 (patch)
tree1b4fa8f2914884602c2f23f11d93824cd8303a72 /migration
parentbdd847a026974634d636e65c4e00cd890cb6099d (diff)
downloadqemu-e8a0f2f9a18f6ab4aa4896cef0010bcad1f323c4.zip
migration: Fix rate limiting issue on RDMA migration
RDMA migration implement save_page function for QEMUFile, but ram_control_save_page do not increase bytes_xfer. So when doing RDMA migration, it will use whole bandwidth. Signed-off-by: Lidong Chen <lidongchen@tencent.com> Message-Id: <1520692378-1835-1-git-send-email-lidongchen@tencent.com> Reviewed-by: Juan Quintela <quintela@redhat.com> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Diffstat (limited to 'migration')
-rw-r--r--migration/qemu-file.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/migration/qemu-file.c b/migration/qemu-file.c
index e85f501f86..bb63c779cc 100644
--- a/migration/qemu-file.c
+++ b/migration/qemu-file.c
@@ -253,7 +253,7 @@ size_t ram_control_save_page(QEMUFile *f, ram_addr_t block_offset,
if (f->hooks && f->hooks->save_page) {
int ret = f->hooks->save_page(f, f->opaque, block_offset,
offset, size, bytes_sent);
-
+ f->bytes_xfer += size;
if (ret != RAM_SAVE_CONTROL_DELAYED) {
if (bytes_sent && *bytes_sent > 0) {
qemu_update_position(f, *bytes_sent);