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 v2 0/3] migration: add speed limit for multifd migration
Date: Tue, 30 Jul 2019 13:33:33 +0800 [thread overview]
Message-ID: <1564464816-21804-1-git-send-email-ivanren@tencent.com> (raw)
From: Ivan Ren <ivanren@tencent.com>
Currently multifd migration has not been limited and it will consume
the whole bandwidth of Nic. These two patches add speed limitation to
it.
This is the v3 patches:
v3 VS v2:
Add Reviewed info and Suggested info.
v2 VS v1:
1. change qemu_file_update_rate_transfer interface name
to qemu_file_update_transfer
2. add a new patch to update ram_counters for multifd sync packet
Ivan Ren (3):
migration: add qemu_file_update_transfer interface
migration: add speed limit for multifd migration
migration: update ram_counters for multifd sync packet
migration/qemu-file.c | 5 +++++
migration/qemu-file.h | 1 +
migration/ram.c | 24 ++++++++++++++----------
3 files changed, 20 insertions(+), 10 deletions(-)
--
2.17.2 (Apple Git-113)
next reply other threads:[~2019-07-30 5:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 5:33 Ivan Ren [this message]
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 ` [Qemu-devel] [PATCH v3 3/3] migration: update ram_counters for multifd sync packet Ivan Ren
2019-08-07 8:46 ` Juan Quintela
2019-08-07 18:53 ` [Qemu-devel] [PATCH v2 0/3] migration: add speed limit for multifd migration Dr. David Alan Gilbert
-- strict thread matches above, loose matches on Subject: below --
2019-07-29 8:01 Ivan Ren
2019-07-30 0:43 ` Wei Yang
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-1-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).