From: Max Reitz <mreitz@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>, John Snow <jsnow@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-stable@nongnu.org" <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] mirror: Only mirror granularity-aligned chunks
Date: Mon, 5 Aug 2019 17:14:52 +0200 [thread overview]
Message-ID: <e7bcdc0f-8950-4f08-e9cb-6b9800201786@redhat.com> (raw)
In-Reply-To: <34fc0ae2-8707-9793-fddc-9fafc899f0ee@virtuozzo.com>
[-- Attachment #1.1: Type: text/plain, Size: 3033 bytes --]
On 05.08.19 17:09, Vladimir Sementsov-Ogievskiy wrote:
> 05.08.2019 17:55, Max Reitz wrote:
>> In write-blocking mode, all writes to the top node directly go to the
>> target. We must only mirror chunks of data that are aligned to the
>> job's granularity, because that is how the dirty bitmap works.
>> Therefore, the request alignment for writes must be the job's
>> granularity (in write-blocking mode).
>>
>> Unfortunately, this forces all reads and writes to have the same
>> granularity (we only need this alignment for writes to the target, not
>> the source), but that is something to be fixed another time.
>>
>> Cc: qemu-stable@nongnu.org
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> ---
>> v2: Fix the placement of our bdrv_refresh_limits() call [Vladimir]
>> ---
>> block/mirror.c | 25 +++++++++++++++++++++++++
>> 1 file changed, 25 insertions(+)
>>
>> diff --git a/block/mirror.c b/block/mirror.c
>> index 8cb75fb409..7f0ff01beb 100644
>> --- a/block/mirror.c
>> +++ b/block/mirror.c
>> @@ -1481,6 +1481,15 @@ static void bdrv_mirror_top_child_perm(BlockDriverState *bs, BdrvChild *c,
>> *nshared = BLK_PERM_ALL;
>> }
>>
>> +static void bdrv_mirror_top_refresh_limits(BlockDriverState *bs, Error **errp)
>> +{
>> + MirrorBDSOpaque *s = bs->opaque;
>> +
>> + if (s && s->job && s->job->copy_mode == MIRROR_COPY_MODE_WRITE_BLOCKING) {
>> + bs->bl.request_alignment = s->job->granularity;
>> + }
>> +}
>> +
>> /* Dummy node that provides consistent read to its users without requiring it
>> * from its backing file and that allows writes on the backing file chain. */
>> static BlockDriver bdrv_mirror_top = {
>> @@ -1493,6 +1502,7 @@ static BlockDriver bdrv_mirror_top = {
>> .bdrv_co_block_status = bdrv_co_block_status_from_backing,
>> .bdrv_refresh_filename = bdrv_mirror_top_refresh_filename,
>> .bdrv_child_perm = bdrv_mirror_top_child_perm,
>> + .bdrv_refresh_limits = bdrv_mirror_top_refresh_limits,
>> };
>>
>> static BlockJob *mirror_start_job(
>> @@ -1637,6 +1647,21 @@ static BlockJob *mirror_start_job(
>> s->should_complete = true;
>> }
>>
>> + /*
>> + * Must be called before we start tracking writes, but after
>> + *
>> + * ((MirrorBlockJob *)
>> + * ((MirrorBDSOpaque *)
>> + * mirror_top_bs->opaque
>> + * )->job
>> + * )->copy_mode
>> + *
>> + * has the correct value.
>> + * (We start tracking writes as of the following
>> + * bdrv_create_dirty_bitmap() call.)
>> + */
>> + bdrv_refresh_limits(mirror_top_bs, &error_abort);
>
> Also, I'm not sure about error_abort() here. why not use local_err and return NULL
> if failed?
Why would it fail?
Max
>> +
>> s->dirty_bitmap = bdrv_create_dirty_bitmap(bs, granularity, NULL, errp);
>> if (!s->dirty_bitmap) {
>> goto fail;
>>
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-05 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 14:55 [Qemu-devel] [PATCH v2] mirror: Only mirror granularity-aligned chunks Max Reitz
2019-08-05 15:09 ` Vladimir Sementsov-Ogievskiy
2019-08-05 15:14 ` Max Reitz [this message]
2019-08-05 15:17 ` Max Reitz
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=e7bcdc0f-8950-4f08-e9cb-6b9800201786@redhat.com \
--to=mreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).