Re: [PATCH 01/21] migration: A rate limit value of 0 is valid

[Cédric Le Goater]

On 5/8/23 15:08, Juan Quintela wrote:

And it is the best way to not have rate_limit.

Signed-off-by: Juan Quintela <quint...@redhat.com>

Reviewed-by: Cédric Le Goater <c...@kaod.org>

C.

---
  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);