From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Cc: "stefanha@redhat.com" <stefanha@redhat.com>,
"fam@euphon.net" <fam@euphon.net>,
"kwolf@redhat.com" <kwolf@redhat.com>,
"mreitz@redhat.com" <mreitz@redhat.com>,
"jsnow@redhat.com" <jsnow@redhat.com>,
"berto@igalia.com" <berto@igalia.com>,
Denis Lunev <den@virtuozzo.com>
Subject: Re: [Qemu-devel] [PATCH v4 3/3] block/stream: introduce a bottom node
Date: Tue, 9 Apr 2019 08:58:08 +0000 [thread overview]
Message-ID: <c977f2bc-914b-e470-5f44-8a72bdb54a41@virtuozzo.com> (raw)
In-Reply-To: <1554747741-918964-4-git-send-email-andrey.shinkevich@virtuozzo.com>
08.04.2019 21:22, Andrey Shinkevich wrote:
> The bottom node is the intermediate block device that has the base as its
> backing image. It is used instead of the base node while a block stream
> job is running to avoid dependency on the base that may change due to the
> parallel jobs. The change may take place due to a filter node as well that
> is inserted between the base and the intermediate bottom node. It occurs
> when the base node is the top one for another commit or stream job.
> After the introduction of the bottom node, don't freeze its backing child,
> that's the base, anymore.
>
> Suggested-by: Vladimir Sementsov-Ogievskiy<vsementsov@virtuozzo.com>
> Signed-off-by: Andrey Shinkevich<andrey.shinkevich@virtuozzo.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
--
Best regards,
Vladimir
WARNING: multiple messages have this Message-ID (diff)
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>,
"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>,
"mreitz@redhat.com" <mreitz@redhat.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"jsnow@redhat.com" <jsnow@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 3/3] block/stream: introduce a bottom node
Date: Tue, 9 Apr 2019 08:58:08 +0000 [thread overview]
Message-ID: <c977f2bc-914b-e470-5f44-8a72bdb54a41@virtuozzo.com> (raw)
Message-ID: <20190409085808.7LlIICk3ARb7cIFHwVSG5weM_iMT9Wzudz6tp1XSGwk@z> (raw)
In-Reply-To: <1554747741-918964-4-git-send-email-andrey.shinkevich@virtuozzo.com>
08.04.2019 21:22, Andrey Shinkevich wrote:
> The bottom node is the intermediate block device that has the base as its
> backing image. It is used instead of the base node while a block stream
> job is running to avoid dependency on the base that may change due to the
> parallel jobs. The change may take place due to a filter node as well that
> is inserted between the base and the intermediate bottom node. It occurs
> when the base node is the top one for another commit or stream job.
> After the introduction of the bottom node, don't freeze its backing child,
> that's the base, anymore.
>
> Suggested-by: Vladimir Sementsov-Ogievskiy<vsementsov@virtuozzo.com>
> Signed-off-by: Andrey Shinkevich<andrey.shinkevich@virtuozzo.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
--
Best regards,
Vladimir
next prev parent reply other threads:[~2019-04-09 8:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 18:22 [Qemu-devel] [PATCH v4 0/3] block/stream: get rid of the base Andrey Shinkevich
2019-04-08 18:22 ` Andrey Shinkevich
2019-04-08 18:22 ` [Qemu-devel] [PATCH v4 1/3] block: include base when checking image chain for block allocation Andrey Shinkevich
2019-04-08 18:22 ` Andrey Shinkevich
2019-04-09 8:57 ` Vladimir Sementsov-Ogievskiy
2019-04-09 8:57 ` Vladimir Sementsov-Ogievskiy
2019-04-09 14:18 ` Alberto Garcia
2019-04-09 14:18 ` Alberto Garcia
2019-04-09 14:43 ` Vladimir Sementsov-Ogievskiy
2019-04-09 14:43 ` Vladimir Sementsov-Ogievskiy
2019-04-09 14:48 ` Alberto Garcia
2019-04-09 14:48 ` Alberto Garcia
2019-04-08 18:22 ` [Qemu-devel] [PATCH v4 2/3] block/stream: refactor stream_run: drop goto Andrey Shinkevich
2019-04-08 18:22 ` Andrey Shinkevich
2019-04-08 18:22 ` [Qemu-devel] [PATCH v4 3/3] block/stream: introduce a bottom node Andrey Shinkevich
2019-04-08 18:22 ` Andrey Shinkevich
2019-04-09 8:58 ` Vladimir Sementsov-Ogievskiy [this message]
2019-04-09 8:58 ` Vladimir Sementsov-Ogievskiy
2019-04-09 13:16 ` Alberto Garcia
2019-04-09 13:16 ` Alberto Garcia
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=c977f2bc-914b-e470-5f44-8a72bdb54a41@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 \
/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).