From: Max Reitz <mreitz@redhat.com>
To: Ren Kimura <rkx1209dev@gmail.com>
Cc: kwolf@redhat.com, qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 1/1] qemu-img: check block status of backing file when converting.
Date: Wed, 27 Apr 2016 13:45:26 +0200 [thread overview]
Message-ID: <5720A656.5050809@redhat.com> (raw)
In-Reply-To: <1461392787-26897-2-git-send-email-rkx1209dev@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 3149 bytes --]
On 23.04.2016 08:26, Ren Kimura wrote:
> When converting images, check the block status of its backing file chain
> to avoid needlessly reading zeros.
>
> Signed-off-by: Ren Kimura <rkx1209dev@gmail.com>
> ---
> qemu-img.c | 31 +++++++++++++++++++++++++++++--
> 1 file changed, 29 insertions(+), 2 deletions(-)
>
> diff --git a/qemu-img.c b/qemu-img.c
> index 06264d9..b771227 100644
> --- a/qemu-img.c
> +++ b/qemu-img.c
> @@ -1451,6 +1451,22 @@ static void convert_select_part(ImgConvertState *s, int64_t sector_num)
> }
> }
>
> +static int64_t get_backing_status(BlockDriverState *bs,
> + int64_t sector_num,
> + int nb_sectors, int *pnum)
> +{
> + while (bs->backing) {
> + int64_t ret;
> + BlockDriverState *file;
> + bs = bs->backing->bs;
> + ret = bdrv_get_block_status(bs, sector_num, nb_sectors, pnum, &file);
> + if (ret < 0 || ret & (BDRV_BLOCK_DATA | BDRV_BLOCK_ZERO)) {
> + return ret;
> + }
Denis' suggestion was to basically drop this function and call
bdrv_get_block_status_above() instead.
I wouldn't strictly oppose keeping this function because of the
BDRV_BLOCK_{DATA,ZERO} vs. BDRV_BLOCK_ALLOCATED issue I talked about before.
One thing we can definitely learn from bdrv_get_block_status_above(),
though, is that a
nb_sectors = MIN(nb_sectors, *pnum);
is missing here (see bdrv_co_get_block_status_above()).
(Sorry for not noticing this before)
> + }
> + return -1;
> +}
> +
> static int convert_iteration_sectors(ImgConvertState *s, int64_t sector_num)
> {
> int64_t ret;
> @@ -1477,10 +1493,21 @@ static int convert_iteration_sectors(ImgConvertState *s, int64_t sector_num)
> } else if (!s->target_has_backing) {
> /* Without a target backing file we must copy over the contents of
> * the backing file as well. */
> - /* TODO Check block status of the backing file chain to avoid
> + /* Check block status of the backing file chain to avoid
> * needlessly reading zeroes and limiting the iteration to the
> * buffer size */
> - s->status = BLK_DATA;
> + ret = get_backing_status(blk_bs(s->src[s->src_cur]),
> + sector_num - s->src_cur_offset,
> + n, &n);
In any case, I think I agree with Denis that just calling
ret = bdrv_get_block_status_above(blk_bs(s->src[s->src_cur]), NULL,
sector_num - s->src_cur_offset, n, &n,
&file);
would be sufficient.
(Sorry for not noticing this either...)
Max
> + if (ret < 0) {
> + return ret;
> + }
> +
> + if (ret & BDRV_BLOCK_ZERO) {
> + s->status = BLK_ZERO;
> + } else {
> + s->status = BLK_DATA;
> + }
> } else {
> s->status = BLK_BACKING_FILE;
> }
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-04-27 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 6:26 [Qemu-devel] [PATCH v4 0/1] qemu-img: check block status of backing file when converting Ren Kimura
2016-04-23 6:26 ` [Qemu-devel] [PATCH v4 1/1] " Ren Kimura
2016-04-27 11:45 ` Max Reitz [this message]
2016-04-27 15:13 ` Ren Kimura
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=5720A656.5050809@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rkx1209dev@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.