From: Max Reitz <mreitz@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org
Cc: kwolf@redhat.com, den@openvz.org, jsnow@redhat.com,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2 2/7] block/block-copy: use block_status
Date: Mon, 17 Feb 2020 12:48:46 +0100 [thread overview]
Message-ID: <168c4ec7-47fa-72a1-dfa7-10754f79519d@redhat.com> (raw)
In-Reply-To: <e6a5a095-78f3-faf1-6eaa-68843b41c490@virtuozzo.com>
[-- Attachment #1.1: Type: text/plain, Size: 2629 bytes --]
On 08.02.20 13:25, Vladimir Sementsov-Ogievskiy wrote:
> 07.02.2020 20:46, Max Reitz wrote:
>> On 27.11.19 19:08, Vladimir Sementsov-Ogievskiy wrote:
>>> Use bdrv_block_status_above to chose effective chunk size and to handle
>>> zeroes effectively.
>>>
>>> This substitutes checking for just being allocated or not, and drops
>>> old code path for it. Assistance by backup job is dropped too, as
>>> caching block-status information is more difficult than just caching
>>> is-allocated information in our dirty bitmap, and backup job is not
>>> good place for this caching anyway.
>>>
>>> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>>> ---
>>> block/block-copy.c | 67 +++++++++++++++++++++++++++++++++++++---------
>>> block/trace-events | 1 +
>>> 2 files changed, 55 insertions(+), 13 deletions(-)
>>>
>>> diff --git a/block/block-copy.c b/block/block-copy.c
>>> index 8602e2cae7..74295d93d5 100644
>>> --- a/block/block-copy.c
>>> +++ b/block/block-copy.c
>>
>> [...]
>>
>>> @@ -336,23 +375,25 @@ int coroutine_fn block_copy(BlockCopyState *s,
>>> chunk_end = next_zero;
>>> }
>>> - if (s->skip_unallocated) {
>>> - ret = block_copy_reset_unallocated(s, start,
>>> &status_bytes);
>>> - if (ret == 0) {
>>> - trace_block_copy_skip_range(s, start, status_bytes);
>>> - start += status_bytes;
>>> - continue;
>>> - }
>>> - /* Clamp to known allocated region */
>>> - chunk_end = MIN(chunk_end, start + status_bytes);
>>> + ret = block_copy_block_status(s, start, chunk_end - start,
>>> + &status_bytes);
>>> + if (s->skip_unallocated && !(ret & BDRV_BLOCK_ALLOCATED)) {
>>> + bdrv_reset_dirty_bitmap(s->copy_bitmap, start,
>>> status_bytes);
>>> + s->progress_reset_callback(s->progress_opaque);
>>> + trace_block_copy_skip_range(s, start, status_bytes);
>>> + start += status_bytes;
>>> + continue;
>>> }
>>> + chunk_end = MIN(chunk_end, start + status_bytes);
>>
>> I’m not sure how much the old “Clamp to known allocated region” actually
>> helps, but I wouldn’t drop it anyway.
>
> But it may be not allocated now. We just clamp to status_bytes.
> It's "known allocated" only if s->skip_unallocated is true.
Ah, yes, I suppose I was just thinking about that case when trying to
understand how the code changes. So:
Reviewed-by: Max Reitz <mreitz@redhat.com>
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-17 12:00 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 18:08 [PATCH v2 for-5.0 0/7] block-copy improvements: part I Vladimir Sementsov-Ogievskiy
2019-11-27 18:08 ` [PATCH v2 1/7] block/block-copy: specialcase first copy_range request Vladimir Sementsov-Ogievskiy
2020-01-29 7:38 ` Andrey Shinkevich
2020-02-07 17:28 ` Max Reitz
2020-02-08 12:32 ` Vladimir Sementsov-Ogievskiy
2019-11-27 18:08 ` [PATCH v2 2/7] block/block-copy: use block_status Vladimir Sementsov-Ogievskiy
2020-01-29 9:12 ` Andrey Shinkevich
2020-02-07 17:46 ` Max Reitz
2020-02-08 12:25 ` Vladimir Sementsov-Ogievskiy
2020-02-17 11:48 ` Max Reitz [this message]
2019-11-27 18:08 ` [PATCH v2 3/7] block/block-copy: factor out block_copy_find_inflight_req Vladimir Sementsov-Ogievskiy
2020-01-29 9:25 ` Andrey Shinkevich
2020-02-07 17:50 ` Max Reitz
2019-11-27 18:08 ` [PATCH v2 4/7] block/block-copy: refactor interfaces to use bytes instead of end Vladimir Sementsov-Ogievskiy
2020-01-29 17:12 ` Andrey Shinkevich
2020-02-05 11:36 ` Vladimir Sementsov-Ogievskiy
2020-02-07 18:01 ` Max Reitz
2020-02-08 12:55 ` Vladimir Sementsov-Ogievskiy
2019-11-27 18:08 ` [PATCH v2 5/7] block/block-copy: rename start to offset in interfaces Vladimir Sementsov-Ogievskiy
2020-01-29 17:37 ` Andrey Shinkevich
2020-02-07 18:04 ` Max Reitz
2019-11-27 18:08 ` [PATCH v2 6/7] block/block-copy: reduce intersecting request lock Vladimir Sementsov-Ogievskiy
2020-01-29 20:05 ` Andrey Shinkevich
2020-01-30 13:45 ` Vladimir Sementsov-Ogievskiy
2020-01-30 16:24 ` Andrey Shinkevich
2020-01-30 17:09 ` Vladimir Sementsov-Ogievskiy
2020-01-30 18:00 ` Andrey Shinkevich
2020-01-30 15:53 ` Andrey Shinkevich
2020-01-30 16:05 ` Vladimir Sementsov-Ogievskiy
2020-02-17 13:38 ` Max Reitz
2020-02-20 7:21 ` Vladimir Sementsov-Ogievskiy
2020-02-20 9:10 ` Max Reitz
2019-11-27 18:08 ` [PATCH v2 7/7] block/block-copy: hide structure definitions Vladimir Sementsov-Ogievskiy
2020-01-30 18:58 ` Andrey Shinkevich
2020-02-17 14:04 ` Max Reitz
2020-02-20 7:26 ` Vladimir Sementsov-Ogievskiy
2019-12-19 9:01 ` [PATCH v2 for-5.0 0/7] block-copy improvements: part I Vladimir Sementsov-Ogievskiy
2020-01-20 9:09 ` Vladimir Sementsov-Ogievskiy
2020-02-07 18:05 ` Max Reitz
2020-02-08 10:28 ` 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=168c4ec7-47fa-72a1-dfa7-10754f79519d@redhat.com \
--to=mreitz@redhat.com \
--cc=den@openvz.org \
--cc=jsnow@redhat.com \
--cc=kwolf@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).