qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hanna Czenczek <hreitz@redhat.com>
To: Alexander Ivanov <alexander.ivanov@virtuozzo.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, den@virtuozzo.com, stefanha@redhat.com,
	vsementsov@yandex-team.ru, kwolf@redhat.com
Subject: Re: [PATCH v8 08/11] parallels: Move check of leaks to a separate function
Date: Wed, 18 Jan 2023 15:48:33 +0100	[thread overview]
Message-ID: <dd8b8623-7749-39ff-e63a-2dd3c30622b0@redhat.com> (raw)
In-Reply-To: <20230115155821.1534598-9-alexander.ivanov@virtuozzo.com>

On 15.01.23 16:58, Alexander Ivanov wrote:
> We will add more and more checks so we need a better code structure
> in parallels_co_check. Let each check performs in a separate loop
> in a separate helper.
>
> Signed-off-by: Alexander Ivanov <alexander.ivanov@virtuozzo.com>
> Reviewed-by: Denis V. Lunev <den@openvz.org>
> ---
>   block/parallels.c | 84 +++++++++++++++++++++++++++++------------------
>   1 file changed, 52 insertions(+), 32 deletions(-)
>
> diff --git a/block/parallels.c b/block/parallels.c
> index 3d06623355..5db099b1dd 100644
> --- a/block/parallels.c
> +++ b/block/parallels.c
> @@ -475,14 +475,14 @@ static int parallels_check_outside_image(BlockDriverState *bs,
>       return 0;
>   }
>   
> -static int coroutine_fn parallels_co_check(BlockDriverState *bs,
> -                                           BdrvCheckResult *res,
> -                                           BdrvCheckMode fix)
> +static int parallels_check_leak(BlockDriverState *bs,
> +                                BdrvCheckResult *res,
> +                                BdrvCheckMode fix)
>   {
>       BDRVParallelsState *s = bs->opaque;
> -    int64_t size, prev_off, high_off;
> -    int ret;
> +    int64_t size, off, high_off, count;
>       uint32_t i;
> +    int ret;
>   
>       size = bdrv_getlength(bs->file->bs);
>       if (size < 0) {
> @@ -490,41 +490,16 @@ static int coroutine_fn parallels_co_check(BlockDriverState *bs,
>           return size;
>       }
>   
> -    qemu_co_mutex_lock(&s->lock);
> -
> -    parallels_check_unclean(bs, res, fix);
> -
> -    ret = parallels_check_outside_image(bs, res, fix);
> -    if (ret < 0) {
> -        goto out;
> -    }
> -
> -    res->bfi.total_clusters = s->bat_size;
> -    res->bfi.compressed_clusters = 0; /* compression is not supported */
> -
>       high_off = 0;
> -    prev_off = 0;
>       for (i = 0; i < s->bat_size; i++) {
> -        int64_t off = bat2sect(s, i) << BDRV_SECTOR_BITS;
> -        if (off == 0) {
> -            prev_off = 0;
> -            continue;
> -        }
> -
> -        res->bfi.allocated_clusters++;
> +        off = bat2sect(s, i) << BDRV_SECTOR_BITS;
>           if (off > high_off) {
>               high_off = off;
>           }
> -
> -        if (prev_off != 0 && (prev_off + s->cluster_size) != off) {
> -            res->bfi.fragmented_clusters++;
> -        }
> -        prev_off = off;
>       }
>   
>       res->image_end_offset = high_off + s->cluster_size;

Continuing the question from patch 7, why do we have separate ways to 
calculate s->data_end and res->image_end_offset now?  Would it be 
possible to just set `res->image_end = s->data_end` and thus drop the 
`for` loop from this function?

Hanna



  reply	other threads:[~2023-01-18 14:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-15 15:58 [PATCH v8 00/11] parallels: Refactor the code of images checks and fix a bug Alexander Ivanov
2023-01-15 15:58 ` [PATCH v8 01/11] parallels: Out of image offset in BAT leads to image inflation Alexander Ivanov
2023-01-15 15:58 ` [PATCH v8 02/11] parallels: Fix high_off calculation in parallels_co_check() Alexander Ivanov
2023-01-15 15:58 ` [PATCH v8 03/11] parallels: Fix data_end after out-of-image check Alexander Ivanov
2023-01-15 15:58 ` [PATCH v8 04/11] parallels: create parallels_set_bat_entry_helper() to assign BAT value Alexander Ivanov
2023-01-15 15:58 ` [PATCH v8 05/11] parallels: Use generic infrastructure for BAT writing in parallels_co_check() Alexander Ivanov
2023-01-15 15:58 ` [PATCH v8 06/11] parallels: Move check of unclean image to a separate function Alexander Ivanov
2023-01-15 15:58 ` [PATCH v8 07/11] parallels: Move check of cluster outside " Alexander Ivanov
2023-01-18 14:45   ` Hanna Czenczek
2023-01-20 10:30     ` Alexander Ivanov
2023-01-15 15:58 ` [PATCH v8 08/11] parallels: Move check of leaks " Alexander Ivanov
2023-01-18 14:48   ` Hanna Czenczek [this message]
2023-01-15 15:58 ` [PATCH v8 09/11] parallels: Move statistic collection " Alexander Ivanov
2023-01-15 15:58 ` [PATCH v8 10/11] parallels: Replace qemu_co_mutex_lock by WITH_QEMU_LOCK_GUARD Alexander Ivanov
2023-01-15 15:58 ` [PATCH v8 11/11] parallels: Incorrect condition in out-of-image check Alexander Ivanov
2023-01-18 14:46   ` Hanna Czenczek
2023-01-20 10:37     ` Alexander Ivanov

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=dd8b8623-7749-39ff-e63a-2dd3c30622b0@redhat.com \
    --to=hreitz@redhat.com \
    --cc=alexander.ivanov@virtuozzo.com \
    --cc=den@virtuozzo.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@yandex-team.ru \
    /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).