From: Max Reitz <mreitz@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Cc: "jcody@redhat.com" <jcody@redhat.com>,
"kwolf@redhat.com" <kwolf@redhat.com>,
"armbru@redhat.com" <armbru@redhat.com>,
"dgilbert@redhat.com" <dgilbert@redhat.com>,
"eblake@redhat.com" <eblake@redhat.com>,
Denis Lunev <den@virtuozzo.com>
Subject: Re: [Qemu-devel] [PATCH v5 1/6] Stream block job involves copy-on-read filter driver
Date: Wed, 9 Jan 2019 14:13:54 +0100 [thread overview]
Message-ID: <cfeff1a6-f515-f5cf-caa2-fb260c0cddc9@redhat.com> (raw)
In-Reply-To: <872d42b0-c794-c104-30a9-fa1296f812d6@virtuozzo.com>
[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]
On 08.01.19 14:45, Vladimir Sementsov-Ogievskiy wrote:
> 30.12.2018 23:09, Andrey Shinkevich wrote:
>> The copy-on-read filter is applied to block-stream operation.
>> It is necessary for further block discard option.
>
> If we move to c-o-r filter in stream, I think we should:
> 1. get rid of COPY_ON_READ flag in stream code (so, this thing to be done in one place)
> 2. add base parameter to c-o-r filter, to not copy things that are below base.
>
> Current behavior of stream is enabling copy-on-read on bs during stream if base == NULL.
> So, if we just add c-o-r filter, we will copy extra blocks. On the other hand, if we
> support base parameter in c-o-r filter we will involve guest reads to the stream
> process for cases with base != NULL, so stream operation should become more efficient.
>
> So for me the following sequence seems reasonable:
>
> - prepare iotests for graph changes
> - add base parameter to c-o-r filter
> - use c-o-r in stream and drop COPY_ON_READ flag from stream code
>
> then (may be in separate series) add discard functionality. And looks like again, it should
> be property of c-o-r filter, not stream job itself, to involve guest reads to discarding too.
>
> In general, Max, is that correspond to what you mean?
Yep, that sounds good to me.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-09 13:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 20:09 [Qemu-devel] [PATCH v5 0/6] Discrad blocks during block-stream operation Andrey Shinkevich
2018-12-30 20:09 ` [Qemu-devel] [PATCH v5 1/6] Stream block job involves copy-on-read filter driver Andrey Shinkevich
2019-01-08 13:45 ` Vladimir Sementsov-Ogievskiy
2019-01-09 13:13 ` Max Reitz [this message]
2019-02-08 12:31 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2018-12-30 20:09 ` [Qemu-devel] [PATCH v5 2/6] Discard blocks while copy-on-read Andrey Shinkevich
2018-12-30 20:09 ` [Qemu-devel] [PATCH v5 3/6] The discard flag for block stream operation Andrey Shinkevich
2019-01-03 10:19 ` Dr. David Alan Gilbert
2018-12-30 20:09 ` [Qemu-devel] [PATCH v5 4/6] iotests: allow resume_drive by node name Andrey Shinkevich
2018-12-30 20:09 ` [Qemu-devel] [PATCH v5 5/6] iotests: prepare 030 for graph change Andrey Shinkevich
2018-12-30 20:09 ` [Qemu-devel] [PATCH v5 6/6] iotests: 030 with block-stream discard Andrey Shinkevich
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=cfeff1a6-f515-f5cf-caa2-fb260c0cddc9@redhat.com \
--to=mreitz@redhat.com \
--cc=andrey.shinkevich@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@virtuozzo.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=jcody@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).