From: Eyal Moscovici <eyal.moscovici@oracle.com>
To: Eric Blake <eblake@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
Max Reitz <mreitz@redhat.com>,
liran.alon@oracle.com, Yoav Elnekave <yoav.elnekave@oracle.com>
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 [thread overview]
Message-ID: <582a5db0-1ca8-e464-5e0b-d7de21d19af8@oracle.com> (raw)
In-Reply-To: <0a3bc115-ea14-4723-2993-6a6c9de12208@redhat.com>
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 <eblake@redhat.com>
>
> 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.
next prev parent reply other threads:[~2020-05-12 9:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 9:11 [PATCH 0/2] Additional parameters for qemu_img map Eyal Moscovici
2020-03-22 9:11 ` [PATCH 1/2] qemu-img: refactor dump_map_entry JSON format output Eyal Moscovici
2020-04-29 14:58 ` Eric Blake
2020-05-06 9:55 ` Eyal Moscovici
2020-03-22 9:11 ` [PATCH 2/2] qemu-img: Add --start-offset and --max-length to map Eyal Moscovici
2020-04-29 15:04 ` Eric Blake
2020-05-06 9:52 ` Eyal Moscovici
2020-04-29 13:39 ` [PATCH 0/2] Additional parameters for qemu_img map John Snow
2020-05-06 21:34 ` [PATCH v2 0/5] " Eyal Moscovici
2020-05-06 21:34 ` [PATCH v2 1/5] qemu-img: remove check that cvtnum value > MAX_INT Eyal Moscovici
2020-05-06 21:49 ` Eric Blake
2020-05-12 9:39 ` Eyal Moscovici
2020-05-12 14:14 ` Eric Blake
2020-05-06 21:34 ` [PATCH v2 2/5] qemu_img: add error report to cvtnum Eyal Moscovici
2020-05-06 21:59 ` Eric Blake
2020-05-12 9:44 ` Eyal Moscovici
2020-05-06 21:34 ` [PATCH v2 3/5] qemu-img: validate image length in img_map Eyal Moscovici
2020-05-06 22:01 ` Eric Blake
2020-05-06 21:34 ` [PATCH v2 4/5] qemu-img: refactor dump_map_entry JSON format output Eyal Moscovici
2020-05-06 21:34 ` [PATCH v2 5/5] qemu-img: Add --start-offset and --max-length to map Eyal Moscovici
2020-05-06 22:04 ` Eric Blake
2020-05-12 9:48 ` Eyal Moscovici [this message]
2020-05-06 21:45 ` [PATCH v2 0/5] Additional parameters for qemu_img map Eric Blake
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=582a5db0-1ca8-e464-5e0b-d7de21d19af8@oracle.com \
--to=eyal.moscovici@oracle.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=liran.alon@oracle.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=yoav.elnekave@oracle.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).