[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH 01/21] migration: A rate limit value of 0 is valid
From: |
Juan Quintela |
Subject: |
[PATCH 01/21] migration: A rate limit value of 0 is valid |
Date: |
Mon, 8 May 2023 15:08:49 +0200 |
And it is the best way to not have rate_limit.
Signed-off-by: Juan Quintela <quintela@redhat.com>
---
migration/migration.c | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/migration/migration.c b/migration/migration.c
index 232e387109..1192f1ebf1 100644
--- a/migration/migration.c
+++ b/migration/migration.c
@@ -2117,12 +2117,7 @@ static int postcopy_start(MigrationState *ms)
* will notice we're in POSTCOPY_ACTIVE and not actually
* wrap their state up here
*/
- /* 0 max-postcopy-bandwidth means unlimited */
- if (!bandwidth) {
- qemu_file_set_rate_limit(ms->to_dst_file, INT64_MAX);
- } else {
- qemu_file_set_rate_limit(ms->to_dst_file, bandwidth /
XFER_LIMIT_RATIO);
- }
+ qemu_file_set_rate_limit(ms->to_dst_file, bandwidth / XFER_LIMIT_RATIO);
if (migrate_postcopy_ram()) {
/* Ping just for debugging, helps line traces up */
qemu_savevm_send_ping(ms->to_dst_file, 2);
--
2.40.0
[PATCH 03/21] migration: We set the rate_limit by a second, Juan Quintela, 2023/05/08