From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, fam@euphon.net, vsementsov@virtuozzo.com,
armbru@redhat.com, mreitz@redhat.com,
nshirokovskiy@virtuozzo.com, den@openvz.org, jsnow@redhat.com
Subject: [Qemu-devel] [PATCH 0/4] qapi: block-dirty-bitmap-remove transaction action
Date: Mon, 3 Jun 2019 15:00:01 +0300 [thread overview]
Message-ID: <20190603120005.37394-1-vsementsov@virtuozzo.com> (raw)
Hi all!
Here is block-dirty-bitmap-remove transaction action.
It is used to do transactional movement of the bitmap (which is
possible in conjunction with merge command). Transactional bitmap
movement is needed in scenarios with external snapshot, when we don't
want to leave copy of the bitmap in the base image.
Implementation itself in 03, in short:
.prepare: make bitmap unnamed and non-persistent, delete stored version
of the bitmap from the image
.commit: release bitmap
.abort: restore bitmap name and persistence. We don't restore bitmap
version in the image. It's not critical, we have in-RAM version,
it will be stored on shutdown
Vladimir Sementsov-Ogievskiy (4):
blockdev: reduce aio_context locked sections in bitmap add/remove
block/dirty-bitmap: add hide/unhide API
qapi: implement block-dirty-bitmap-remove transaction action
iotests: test bitmap moving inside 254
qapi/transaction.json | 2 +
include/block/dirty-bitmap.h | 2 +
block/dirty-bitmap.c | 26 +++++++++
blockdev.c | 100 +++++++++++++++++++++++++++--------
tests/qemu-iotests/254 | 30 ++++++++++-
tests/qemu-iotests/254.out | 82 ++++++++++++++++++++++++++++
6 files changed, 219 insertions(+), 23 deletions(-)
--
2.18.0
next reply other threads:[~2019-06-03 12:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 12:00 Vladimir Sementsov-Ogievskiy [this message]
2019-06-03 12:00 ` [Qemu-devel] [PATCH 1/4] blockdev: reduce aio_context locked sections in bitmap add/remove Vladimir Sementsov-Ogievskiy
2019-06-07 22:28 ` John Snow
2019-06-03 12:00 ` [Qemu-devel] [PATCH 2/4] block/dirty-bitmap: add hide/unhide API Vladimir Sementsov-Ogievskiy
2019-06-07 22:39 ` John Snow
2019-06-10 9:33 ` Vladimir Sementsov-Ogievskiy
2019-06-10 9:42 ` Vladimir Sementsov-Ogievskiy
2019-06-10 9:44 ` Vladimir Sementsov-Ogievskiy
2019-06-10 9:46 ` Vladimir Sementsov-Ogievskiy
2019-06-03 12:00 ` [Qemu-devel] [PATCH 3/4] qapi: implement block-dirty-bitmap-remove transaction action Vladimir Sementsov-Ogievskiy
2019-06-07 22:57 ` John Snow
2019-06-10 9:39 ` Vladimir Sementsov-Ogievskiy
2019-06-03 12:00 ` [Qemu-devel] [PATCH 4/4] iotests: test bitmap moving inside 254 Vladimir Sementsov-Ogievskiy
2019-06-07 22:26 ` [Qemu-devel] [PATCH 0/4] qapi: block-dirty-bitmap-remove transaction action John Snow
2019-06-17 11:37 ` Vladimir Sementsov-Ogievskiy
2019-06-17 16:03 ` Kevin Wolf
2019-06-18 7:31 ` Vladimir Sementsov-Ogievskiy
2019-06-18 7:37 ` Kevin Wolf
2019-06-28 0:25 ` John Snow
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=20190603120005.37394-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=nshirokovskiy@virtuozzo.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).