commit 2c59fd833a6c547e174b26ba3e1f88f5865e16cf
author Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> Sun Jan 17 00:46:52 2021 +0300
committer Max Reitz <mreitz@redhat.com> Tue Jan 26 14:36:37 2021 +0100
tree bac9d428e1078b7dbfb2e86415068cae5b1b9086
parent 3ee1483b95f314b960231c1c0b329bea4346f49c

qapi: backup: add max-chunk and max-workers to x-perf struct

Add new parameters to configure future backup features. The patch
doesn't introduce aio backup requests (so we actually have only one
worker) neither requests larger than one cluster. Still, formally we
satisfy these maximums anyway, so add the parameters now, to facilitate
further patch which will really change backup job behavior.

Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20210116214705.822267-11-vsementsov@virtuozzo.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>

blockdev.c

diff --git a/blockdev.c b/blockdev.c
index fc88dc0..25aaacf 100644
--- a/blockdev.c
+++ b/blockdev.c
@@ -2829,7 +2829,7 @@
 {
     BlockJob *job = NULL;
     BdrvDirtyBitmap *bmap = NULL;
-    BackupPerf perf = { .use_copy_range = true };
+    BackupPerf perf = { .use_copy_range = true, .max_workers = 64 };
     int job_flags = JOB_DEFAULT;
 
     if (!backup->has_speed) {
@@ -2858,6 +2858,12 @@
         if (backup->x_perf->has_use_copy_range) {
             perf.use_copy_range = backup->x_perf->use_copy_range;
         }
+        if (backup->x_perf->has_max_workers) {
+            perf.max_workers = backup->x_perf->max_workers;
+        }
+        if (backup->x_perf->has_max_chunk) {
+            perf.max_chunk = backup->x_perf->max_chunk;
+        }
     }
 
     if ((backup->sync == MIRROR_SYNC_MODE_BITMAP) ||