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: "fam@euphon.net" <fam@euphon.net>,
"kwolf@redhat.com" <kwolf@redhat.com>,
"berto@igalia.com" <berto@igalia.com>,
Denis Lunev <den@virtuozzo.com>,
"wencongyang2@huawei.com" <wencongyang2@huawei.com>,
"xiechanglong.d@gmail.com" <xiechanglong.d@gmail.com>,
"mreitz@redhat.com" <mreitz@redhat.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>,
"jsnow@redhat.com" <jsnow@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 0/3] block/stream: get rid of the base
Date: Tue, 21 May 2019 07:51:51 +0000 [thread overview]
Message-ID: <e04dd957-4b8f-eed4-f865-74fe2ccf45fd@virtuozzo.com> (raw)
In-Reply-To: <20190506153429.52737-1-vsementsov@virtuozzo.com>
ping
06.05.2019 18:34, Vladimir Sementsov-Ogievskiy wrote:
> This series introduces a bottom intermediate node that eliminates the
> dependency on the base that may change while stream job is running.
> It happens when stream/commit parallel jobs are running on the same
> backing chain. The base node of the stream job may be a top node of
> the parallel commit job and can change before the stream job is
> completed. We avoid that dependency by introducing the bottom node.
>
> v6: [resend by Vladimir]
> 01: improve comment in block/io.c, suggested by Alberto
>
> v5: [resend by Vladimir]
> 01: use comment wording in block/io.c suggested by Alberto
> Now the whole series are reviewed-by Alberto and me.
>
> v4:
> trace_stream_start reverted to the base.
> bdrv_is_allocated_above_inclusive() deleted and the new parameter
> 'bool include_base' was added to the bdrv_is_allocated_above().
>
> Andrey Shinkevich (2):
> block: include base when checking image chain for block allocation
> block/stream: introduce a bottom node
>
> Vladimir Sementsov-Ogievskiy (1):
> block/stream: refactor stream_run: drop goto
>
> include/block/block.h | 3 +-
> block/commit.c | 2 +-
> block/io.c | 20 ++++++++++----
> block/mirror.c | 2 +-
> block/replication.c | 2 +-
> block/stream.c | 62 ++++++++++++++++++++----------------------
> tests/qemu-iotests/245 | 4 +--
> 7 files changed, 50 insertions(+), 45 deletions(-)
>
--
Best regards,
Vladimir
prev parent reply other threads:[~2019-05-21 7:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 15:34 [Qemu-devel] [PATCH v6 0/3] block/stream: get rid of the base Vladimir Sementsov-Ogievskiy
2019-05-06 15:34 ` [Qemu-devel] [PATCH v6 1/3] block: include base when checking image chain for block allocation Vladimir Sementsov-Ogievskiy
2019-05-28 17:15 ` Max Reitz
2019-05-06 15:34 ` [Qemu-devel] [PATCH v6 2/3] block/stream: refactor stream_run: drop goto Vladimir Sementsov-Ogievskiy
2019-05-28 17:17 ` Max Reitz
2019-05-06 15:34 ` [Qemu-devel] [PATCH v6 3/3] block/stream: introduce a bottom node Vladimir Sementsov-Ogievskiy
2019-05-28 17:33 ` Max Reitz
2019-05-29 7:34 ` Vladimir Sementsov-Ogievskiy
2019-05-29 11:23 ` Max Reitz
2019-05-29 11:44 ` Vladimir Sementsov-Ogievskiy
2019-05-29 11:53 ` Max Reitz
2019-05-21 7:51 ` Vladimir Sementsov-Ogievskiy [this message]
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=e04dd957-4b8f-eed4-f865-74fe2ccf45fd@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=andrey.shinkevich@virtuozzo.com \
--cc=berto@igalia.com \
--cc=den@virtuozzo.com \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wencongyang2@huawei.com \
--cc=xiechanglong.d@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 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).