qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Cc: "pbonzini@redhat.com" <pbonzini@redhat.com>,
	"eblake@redhat.com" <eblake@redhat.com>,
	"jsnow@redhat.com" <jsnow@redhat.com>,
	"famz@redhat.com" <famz@redhat.com>,
	"mreitz@redhat.com" <mreitz@redhat.com>,
	"kwolf@redhat.com" <kwolf@redhat.com>,
	"jcody@redhat.com" <jcody@redhat.com>,
	Denis Lunev <den@virtuozzo.com>
Subject: [Qemu-devel] ping2 Re: [PATCH v4 0/8] dirty-bitmap: rewrite bdrv_dirty_iter_next_area
Date: Wed, 12 Dec 2018 09:27:38 +0000	[thread overview]
Message-ID: <504d170c-56ee-0cf5-78e0-47aded4c132f@virtuozzo.com> (raw)
In-Reply-To: <20180917145732.48590-1-vsementsov@virtuozzo.com>

ping. No dependencies, apply to master.

17.09.2018 17:57, Vladimir Sementsov-Ogievskiy wrote:
> Hi all.
> 
> 1. bdrv_dirty_iter_next_area don't use hbitmap_next_zero and uses
> inefficient loop instead. Let's improve it.
> 
> 2. bdrv_dirty_iter_next_area don't handle unaligned offset and
> max_offset correctly. I'm not sure that it is a real bug. But if it is,
> we need these series in 3.0.
> 
> Details are in 05 commit message.
> 
> Note: "[PATCH] nbd/server: fix bitmap export" should be applied first:
> Based-on: <20180914165116.23182-1-vsementsov@virtuozzo.com>
> 
> v4:
> 
> Rework: switch interface to start,count / offset,bytes style.
> Fix wrong handling of the case when requested region end exceeds
> overall bitmap end.
> Some other changes.
> 
> 06-08: add John's r-b.
> 
> v3:
> 01: - change interface to start/end, and -1 as special end-marker instead of 0
>      - "not found" for invalid regions instead of assert
> 02: rebase on 01 changes
> 03: - fix mistake in hbitmap_iter_init arguments (mistake in
>        hbitmap_next_zero arguments is fixed automatically due to 01 changes)
> 04: new
> 
> 
> v2:
> 
> 01: - improve comment
>      - s/bytes/count/
>      - fix forgotten function call in test
>      - introduce orig_size field here for HBitmap,
>        make checking in hbitmap_next_zero more effective and safe
> 02: new
> 03: - orig_size already introduced in 01
>      - fix hbitmap_next_dirty_area to not return value less than
>        offset on unaligned requests
> 
> Vladimir Sementsov-Ogievskiy (8):
>    dirty-bitmap: improve bdrv_dirty_bitmap_next_zero
>    tests: add tests for hbitmap_next_zero with specified end parameter
>    dirty-bitmap: add bdrv_dirty_bitmap_next_dirty_area
>    tests: add tests for hbitmap_next_dirty_area
>    block/mirror: fix and improve do_sync_target_write
>    Revert "block/dirty-bitmap: Add bdrv_dirty_iter_next_area"
>    Revert "test-hbitmap: Add non-advancing iter_next tests"
>    Revert "hbitmap: Add @advance param to hbitmap_iter_next()"
> 
>   include/block/dirty-bitmap.h |   7 +-
>   include/qemu/hbitmap.h       |  31 ++++--
>   block/backup.c               |   5 +-
>   block/dirty-bitmap.c         |  68 ++------------
>   block/mirror.c               |  17 ++--
>   nbd/server.c                 |   2 +-
>   tests/test-hbitmap.c         | 177 +++++++++++++++++++++++++++++------
>   util/hbitmap.c               |  76 ++++++++++++---
>   8 files changed, 262 insertions(+), 121 deletions(-)
> 


-- 
Best regards,
Vladimir

  parent reply	other threads:[~2018-12-12  9:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180917145732.48590-1-vsementsov@virtuozzo.com>
2018-10-11 15:38 ` [Qemu-devel] ping Re: [PATCH v4 0/8] dirty-bitmap: rewrite bdrv_dirty_iter_next_area Vladimir Sementsov-Ogievskiy
2018-12-12  9:27 ` Vladimir Sementsov-Ogievskiy [this message]
2018-12-12 20:41   ` [Qemu-devel] ping2 " John Snow
2018-12-13 11:07     ` Vladimir Sementsov-Ogievskiy
2018-12-13 18:18       ` John Snow
2018-12-13 20:06         ` Denis Lunev

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=504d170c-56ee-0cf5-78e0-47aded4c132f@virtuozzo.com \
    --to=vsementsov@virtuozzo.com \
    --cc=den@virtuozzo.com \
    --cc=eblake@redhat.com \
    --cc=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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).