From: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: jcody@redhat.com, kwolf@redhat.com, mreitz@redhat.com,
armbru@redhat.com, dgilbert@redhat.com, eblake@redhat.com,
den@openvz.org, vsementsov@virtuozzo.com,
andrey.shinkevich@virtuozzo.com
Subject: [Qemu-devel] [PATCH 0/2] Discrad blocks during block-stream operation
Date: Wed, 31 Oct 2018 19:47:18 +0300 [thread overview]
Message-ID: <1541004440-182262-1-git-send-email-andrey.shinkevich@virtuozzo.com> (raw)
Hello everyone!
The given feature discards blocks with copy-on-read operation while the
streaming process runs. Adding the 'discard' argument to the QMP block-stream
command allows dropping a block in the backing chain after it has been copied
to the active layer. That will elude the block duplication in the intermediate
backing file. It saves the disk space while external snapshots are being
merged.
The method involves the filter insertion above the active layer to allow write
operation in the backing chain. The method is similar to that in the 'commit
active' command (mirror.c).
Andrey Shinkevich (2):
The discard flag for block stream operation
Discard blocks while copy-on-read
block/stream.c | 402 ++++++++++++++++++++++++++++++++++++++++++++--
blockdev.c | 8 +-
hmp-commands.hx | 4 +-
hmp.c | 4 +-
include/block/block_int.h | 2 +-
qapi/block-core.json | 5 +-
6 files changed, 407 insertions(+), 18 deletions(-)
--
1.8.3.1
next reply other threads:[~2018-10-31 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 16:47 Andrey Shinkevich [this message]
2018-10-31 16:47 ` [Qemu-devel] [PATCH 1/2] The discard flag for block stream operation Andrey Shinkevich
2018-10-31 17:38 ` Dr. David Alan Gilbert
2018-11-06 11:34 ` Andrey Shinkevich
2018-11-05 16:08 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2018-11-06 11:35 ` Andrey Shinkevich
2018-10-31 16:47 ` [Qemu-devel] [PATCH 2/2] Discard blocks while copy-on-read 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=1541004440-182262-1-git-send-email-andrey.shinkevich@virtuozzo.com \
--to=andrey.shinkevich@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).