From: Anton Nefedov <anton.nefedov@virtuozzo.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, den@virtuozzo.com, kwolf@redhat.com,
mreitz@redhat.com, eblake@redhat.com,
Anton Nefedov <anton.nefedov@virtuozzo.com>
Subject: [Qemu-devel] [PATCH v3 00/13] qcow2: space preallocation and COW improvements
Date: Mon, 31 Jul 2017 19:21:52 +0300 [thread overview]
Message-ID: <1501518125-29851-1-git-send-email-anton.nefedov@virtuozzo.com> (raw)
Here goes a revisited series on qcow2 preallocation. It's probably a bit better
integrated this time and the amount of code is reduced significantly.
Changes in v3:
- requests intersection detection from the previous versions is removed
from qcow2 driver. Instead, tracked request infrastructure from the common
block layer is used.
- that made possible to omit preallocation for metadata writes.
Those are rare and won't affect performance.
- 'Simultaneous writes' feature (patches v2 12-15) dropped by now;
Might worth a separate series.
- various remarks to the previous version fixed
- some iotests added
========
Changes in v2:
- introduce new BDRV flag for write_zeroes()
instead of using driver callback directly.
Skipped introducing new functions like bdrv_co_pallocate() for now:
1. it seems ok to keep calling this write_zeroes() as zeroes
are expected;
2. most of the code can be reused now anyway, so changes to
write_zeroes() path are not significant
3. write_zeroes() alignment and max-request limits can also be reused
As a possible alternative we can have bdrv_co_pallocate() which can
switch to pwrite_zeroes(,flags|=BDRV_REQ_ALLOCATE) early.
========
This pull request is to address a few performance problems of qcow2 format:
1. non cluster-aligned write requests (to unallocated clusters) explicitly
pad data with zeroes if there is no backing data. This can be avoided
and the whole clusters are preallocated and zeroed in a single
efficient write_zeroes() operation, also providing better host file
continuity
2. moreover, efficient write_zeroes() operation can be used to preallocate
space megabytes ahead which gives noticeable improvement on some storage
types (e.g. distributed storages where space allocation operation is
expensive)
/* omitted in v3: */
3. preallocating/zeroing the clusters in advance makes possible to enable
simultaneous writes to the same unallocated cluster, which is beneficial
for parallel sequential write operations which are not cluster-aligned
Performance test results are added to commit messages (see patch 3, 12)
Anton Nefedov (10):
block: introduce BDRV_REQ_ALLOCATE flag
block: treat BDRV_REQ_ALLOCATE as serialising
file-posix: support BDRV_REQ_ALLOCATE
block: support BDRV_REQ_ALLOCATE in passthrough drivers
qcow2: set inactive flag
qcow2: move is_zero_sectors() up
qcow2: skip writing zero buffers to empty COW areas
qcow2: allocate image space by-cluster
iotest 190: test BDRV_REQ_ALLOCATE
iotest 134: test cluster-misaligned encrypted write
Denis V. Lunev (2):
qcow2: preallocation at image expand
qcow2: truncate preallocated space
Pavel Butsykin (1):
qcow2: check space leak at the end of the image
include/block/block.h | 6 +-
include/block/block_int.h | 2 +-
block/qcow2.h | 18 ++++
block/blkdebug.c | 3 +-
block/file-posix.c | 9 +-
block/io.c | 47 +++++++--
block/qcow2-cluster.c | 14 ++-
block/qcow2-refcount.c | 7 ++
block/qcow2.c | 201 +++++++++++++++++++++++++++++++++----
block/raw-format.c | 3 +-
block/trace-events | 2 +
qemu-options.hx | 4 +
tests/qemu-iotests/026.out | 104 ++++++++++++++-----
tests/qemu-iotests/026.out.nocache | 104 ++++++++++++++-----
tests/qemu-iotests/029.out | 5 +-
tests/qemu-iotests/060 | 2 +-
tests/qemu-iotests/060.out | 13 ++-
tests/qemu-iotests/061.out | 5 +-
tests/qemu-iotests/066 | 2 +-
tests/qemu-iotests/066.out | 9 +-
tests/qemu-iotests/098.out | 7 +-
tests/qemu-iotests/108.out | 5 +-
tests/qemu-iotests/112.out | 5 +-
tests/qemu-iotests/134 | 9 ++
tests/qemu-iotests/134.out | 10 ++
tests/qemu-iotests/190 | 146 +++++++++++++++++++++++++++
tests/qemu-iotests/190.out | 50 +++++++++
tests/qemu-iotests/group | 1 +
28 files changed, 693 insertions(+), 100 deletions(-)
create mode 100755 tests/qemu-iotests/190
create mode 100644 tests/qemu-iotests/190.out
--
2.7.4
next reply other threads:[~2017-07-31 16:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 16:21 Anton Nefedov [this message]
2017-07-31 16:21 ` [Qemu-devel] [PATCH v3 01/13] block: introduce BDRV_REQ_ALLOCATE flag Anton Nefedov
2017-07-31 16:21 ` [Qemu-devel] [PATCH v3 02/13] block: treat BDRV_REQ_ALLOCATE as serialising Anton Nefedov
2017-07-31 16:21 ` [Qemu-devel] [PATCH v3 03/13] file-posix: support BDRV_REQ_ALLOCATE Anton Nefedov
2017-07-31 16:21 ` [Qemu-devel] [PATCH v3 04/13] block: support BDRV_REQ_ALLOCATE in passthrough drivers Anton Nefedov
2017-07-31 19:11 ` Eric Blake
2017-08-01 12:58 ` Anton Nefedov
2017-07-31 16:21 ` [Qemu-devel] [PATCH v3 05/13] qcow2: preallocation at image expand Anton Nefedov
2017-07-31 16:21 ` [Qemu-devel] [PATCH v3 06/13] qcow2: set inactive flag Anton Nefedov
2017-07-31 16:21 ` [Qemu-devel] [PATCH v3 07/13] qcow2: truncate preallocated space Anton Nefedov
2017-07-31 16:22 ` [Qemu-devel] [PATCH v3 08/13] qcow2: check space leak at the end of the image Anton Nefedov
2017-07-31 16:22 ` [Qemu-devel] [PATCH v3 09/13] qcow2: move is_zero_sectors() up Anton Nefedov
2017-07-31 19:13 ` Eric Blake
2017-08-01 12:59 ` Anton Nefedov
2017-07-31 16:22 ` [Qemu-devel] [PATCH v3 10/13] qcow2: skip writing zero buffers to empty COW areas Anton Nefedov
2017-07-31 16:22 ` [Qemu-devel] [PATCH v3 11/13] qcow2: allocate image space by-cluster Anton Nefedov
2017-07-31 16:22 ` [Qemu-devel] [PATCH v3 12/13] iotest 190: test BDRV_REQ_ALLOCATE Anton Nefedov
2017-07-31 16:22 ` [Qemu-devel] [PATCH v3 13/13] iotest 134: test cluster-misaligned encrypted write Anton Nefedov
2017-07-31 16:39 ` [Qemu-devel] [PATCH v3 00/13] qcow2: space preallocation and COW improvements no-reply
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=1501518125-29851-1-git-send-email-anton.nefedov@virtuozzo.com \
--to=anton.nefedov@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.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).