From: Eric Blake <eblake@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: kwolf@redhat.com, qemu-block@nongnu.org,
nikita.lapshin@virtuozzo.com, qemu-devel@nongnu.org,
nsoffer@redhat.com, hreitz@redhat.com, den@openvz.org,
jsnow@redhat.com
Subject: Re: [PATCH v3 3/4] qemu-img: add --shallow option for qemu-img compare
Date: Fri, 29 Oct 2021 15:44:02 -0500 [thread overview]
Message-ID: <20211029204402.flo6xeps4pexlujg@redhat.com> (raw)
In-Reply-To: <20211028102441.1878668-4-vsementsov@virtuozzo.com>
On Thu, Oct 28, 2021 at 12:24:40PM +0200, Vladimir Sementsov-Ogievskiy wrote:
> Allow compare only top images of backing chains. This is useful to
Allow the comparison of only the top image of backing chains.
> compare images with same backing file or to compare incremental images
> from the chain of incremental backups with "--stat" option.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> Reviewed-by: Hanna Reitz <hreitz@redhat.com>
> ---
> docs/tools/qemu-img.rst | 9 ++++++++-
> qemu-img.c | 8 ++++++--
> qemu-img-cmds.hx | 4 ++--
> 3 files changed, 16 insertions(+), 5 deletions(-)
>
> diff --git a/docs/tools/qemu-img.rst b/docs/tools/qemu-img.rst
> index 9bfdd93d6c..c6e9306c70 100644
> --- a/docs/tools/qemu-img.rst
> +++ b/docs/tools/qemu-img.rst
> @@ -176,6 +176,13 @@ Parameters to compare subcommand:
> - If both files don't specify cluster-size, use default of 64K
> - If only one file specifies cluster-size, just use that.
>
> +.. option:: --shallow
> +
> + This option prevents opening and comparing any backing files.
> + This is useful to compare images with same backing file or to compare
> + incremental images from the chain of incremental backups with
> + ``--stat`` option.
If I understand correctly, your implementation makes --shallow an
all-or-none option (either both images are compared shallow, or
neither is). Does it make sense to make it a per-image option
(--shallow-source, --shallow-dest), where --shallow is a synonym for
the more verbose --shallow-source --shallow-dest?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2021-10-29 20:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 10:24 [PATCH v3 0/4] qemu-img compare --stat Vladimir Sementsov-Ogievskiy
2021-10-28 10:24 ` [PATCH v3 1/4] qemu-img: implement " Vladimir Sementsov-Ogievskiy
2021-10-29 20:25 ` Eric Blake
2021-11-02 12:40 ` Hanna Reitz
2021-10-28 10:24 ` [PATCH v3 2/4] qemu-img: make --block-size optional for " Vladimir Sementsov-Ogievskiy
2021-10-29 20:32 ` Eric Blake
2021-11-01 8:03 ` Vladimir Sementsov-Ogievskiy
2021-11-01 14:19 ` Eric Blake
2021-11-02 12:48 ` Hanna Reitz
2021-10-28 10:24 ` [PATCH v3 3/4] qemu-img: add --shallow option for qemu-img compare Vladimir Sementsov-Ogievskiy
2021-10-29 20:44 ` Eric Blake [this message]
2021-11-01 8:22 ` Vladimir Sementsov-Ogievskiy
2021-10-28 10:24 ` [PATCH v3 4/4] iotests: add qemu-img-compare-stat test Vladimir Sementsov-Ogievskiy
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=20211029204402.flo6xeps4pexlujg@redhat.com \
--to=eblake@redhat.com \
--cc=den@openvz.org \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=nikita.lapshin@virtuozzo.com \
--cc=nsoffer@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).