qemu-block
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v2 5/5] qemu-img: Add --start-offset and --max-length to map


From: Eyal Moscovici
Subject: Re: [PATCH v2 5/5] qemu-img: Add --start-offset and --max-length to map
Date: Tue, 12 May 2020 12:48:13 +0300
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.8.0


On 07/05/2020 1:04, Eric Blake wrote:
On 5/6/20 4:34 PM, Eyal Moscovici wrote:
The mapping operation of large disks especially ones stored over a
long chain of QCOW2 files can take a long time to finish.
Additionally when mapping fails there was no way recover by
restarting the mapping from the failed location.

The new options, --start-offset and --max-length allows the user to
divide these type of map operations into shorter independent tasks.

Reviewed-by: Eric Blake <address@hidden>

This patch has some changes from v1.  Among others,...

@@ -3041,6 +3045,18 @@ static int img_map(int argc, char **argv)
          case OPTION_OUTPUT:
              output = optarg;
              break;
+        case 's':
+            start_offset = cvtnum("start offset", optarg);
+            if (start_offset < 0) {
+                return 1;
+            }
+            break;

the new semantics of cvtnum() in this series is enough of a difference that I would have removed R-b to make sure the updated patch gets re-reviewed, if it had been me as author.  But in this case, it does look like the changes are all addressed to comments I suggested in v1, so I'm fine that you left my R-b.

Ok, got it.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]