From: Eric Blake <eblake@redhat.com>
To: Anton Nefedov <anton.nefedov@virtuozzo.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, den@virtuozzo.com, kwolf@redhat.com,
mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 03/15] block: introduce BDRV_REQ_ALLOCATE flag
Date: Fri, 4 Aug 2017 14:51:34 -0500 [thread overview]
Message-ID: <e47643b2-ff2e-ca38-e666-d89a28f0c46f@redhat.com> (raw)
In-Reply-To: <1501597152-25342-4-git-send-email-anton.nefedov@virtuozzo.com>
[-- Attachment #1: Type: text/plain, Size: 3466 bytes --]
On 08/01/2017 09:19 AM, Anton Nefedov wrote:
> The flag is supposed to indicate that the region of the disk image has
> to be sufficiently allocated so it reads as zeroes. The call with the flag
> set has to return -ENOTSUP if allocation cannot be done efficiently
> (i.e. without falling back to writing actual buffers)
>
> Signed-off-by: Anton Nefedov <anton.nefedov@virtuozzo.com>
> ---
> include/block/block.h | 6 +++++-
> include/block/block_int.h | 2 +-
> block/io.c | 20 +++++++++++++++++---
> 3 files changed, 23 insertions(+), 5 deletions(-)
Reviewed-by: Eric Blake <eblake@redhat.com>
You might want the commit message to be a bit more verbose...
>
> diff --git a/include/block/block.h b/include/block/block.h
> index 7fe0125..828da67 100644
> --- a/include/block/block.h
> +++ b/include/block/block.h
> @@ -65,9 +65,13 @@ typedef enum {
> BDRV_REQ_NO_SERIALISING = 0x8,
> BDRV_REQ_FUA = 0x10,
> BDRV_REQ_WRITE_COMPRESSED = 0x20,
> + /* The BDRV_REQ_ALLOCATE flag is used to indicate that the driver has to
> + * efficiently allocate the space so it reads as zeroes, or return an error.
> + */
> + BDRV_REQ_ALLOCATE = 0x40,
>
> /* Mask of valid flags */
> - BDRV_REQ_MASK = 0x3f,
> + BDRV_REQ_MASK = 0x7f,
> } BdrvRequestFlags;
>
> typedef struct BlockSizes {
> diff --git a/include/block/block_int.h b/include/block/block_int.h
> index 9b94b32..9b64411 100644
> --- a/include/block/block_int.h
> +++ b/include/block/block_int.h
> @@ -585,7 +585,7 @@ struct BlockDriverState {
> /* Flags honored during pwrite (so far: BDRV_REQ_FUA) */
> unsigned int supported_write_flags;
> /* Flags honored during pwrite_zeroes (so far: BDRV_REQ_FUA,
> - * BDRV_REQ_MAY_UNMAP) */
> + * BDRV_REQ_MAY_UNMAP, BDRV_REQ_ALLOCATE) */
> unsigned int supported_zero_flags;
...in addition to adding the new flag here and documenting its semantics
for drivers...
>
> /* the following member gives a name to every node on the bs graph. */
> diff --git a/block/io.c b/block/io.c
> index 375fc66..04d495e 100644
> --- a/block/io.c
> +++ b/block/io.c
> @@ -1245,7 +1245,7 @@ static int coroutine_fn bdrv_co_do_pwrite_zeroes(BlockDriverState *bs,
> assert(!bs->supported_zero_flags);
> }
>
> - if (ret == -ENOTSUP) {
> + if (ret == -ENOTSUP && !(flags & BDRV_REQ_ALLOCATE)) {
> /* Fall back to bounce buffer if write zeroes is unsupported */
> BdrvRequestFlags write_flags = flags & ~BDRV_REQ_ZERO_WRITE;
...you also made sure that anywhere the flag is in use you avoid a slow
fallback...
> @@ -1639,6 +1645,14 @@ int coroutine_fn bdrv_co_pwrite_zeroes(BdrvChild *child, int64_t offset,
> {
> trace_bdrv_co_pwrite_zeroes(child->bs, offset, bytes, flags);
>
> + assert(!(flags & BDRV_REQ_MAY_UNMAP && flags & BDRV_REQ_ALLOCATE));
> +
> + if (flags & BDRV_REQ_ALLOCATE &&
> + !(child->bs->supported_zero_flags & BDRV_REQ_ALLOCATE))
> + {
> + return -ENOTSUP;
...as well as providing a sane default to make the flag always trigger
-ENOTSUP until individual drivers implement something in later patches.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-08-04 19:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 14:18 [Qemu-devel] [PATCH v4 00/15] qcow2: space preallocation and COW improvements Anton Nefedov
2017-08-01 14:18 ` [Qemu-devel] [PATCH v4 01/15] mirror: inherit supported write/zero flags Anton Nefedov
2017-08-04 15:13 ` [Qemu-devel] [PATCH v4 for-2.10 " Eric Blake
2017-08-01 14:18 ` [Qemu-devel] [PATCH v4 02/15] blkverify: set " Anton Nefedov
2017-08-04 15:23 ` Eric Blake
2017-08-07 12:19 ` Anton Nefedov
2017-08-01 14:19 ` [Qemu-devel] [PATCH v4 03/15] block: introduce BDRV_REQ_ALLOCATE flag Anton Nefedov
2017-08-04 19:51 ` Eric Blake [this message]
2017-08-29 12:47 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2017-08-01 14:19 ` [Qemu-devel] [PATCH v4 04/15] block: treat BDRV_REQ_ALLOCATE as serialising Anton Nefedov
2017-08-01 14:19 ` [Qemu-devel] [PATCH v4 05/15] file-posix: support BDRV_REQ_ALLOCATE Anton Nefedov
2017-08-29 13:00 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2017-08-01 14:19 ` [Qemu-devel] [PATCH v4 06/15] block: support BDRV_REQ_ALLOCATE in passthrough drivers Anton Nefedov
2017-08-29 13:07 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2017-08-01 14:19 ` [Qemu-devel] [PATCH v4 07/15] qcow2: preallocation at image expand Anton Nefedov
2017-08-01 14:19 ` [Qemu-devel] [PATCH v4 08/15] qcow2: set inactive flag Anton Nefedov
2017-08-04 20:00 ` Eric Blake
2017-08-07 12:06 ` Anton Nefedov
2017-08-01 14:19 ` [Qemu-devel] [PATCH v4 09/15] qcow2: truncate preallocated space Anton Nefedov
2017-08-01 14:19 ` [Qemu-devel] [PATCH v4 10/15] qcow2: check space leak at the end of the image Anton Nefedov
2017-08-01 14:19 ` [Qemu-devel] [PATCH v4 11/15] qcow2: move is_zero() up Anton Nefedov
2017-08-01 14:19 ` [Qemu-devel] [PATCH v4 12/15] qcow2: skip writing zero buffers to empty COW areas Anton Nefedov
2017-08-01 14:19 ` [Qemu-devel] [PATCH v4 13/15] qcow2: allocate image space by-cluster Anton Nefedov
2017-08-01 14:19 ` [Qemu-devel] [PATCH v4 14/15] iotest 190: test BDRV_REQ_ALLOCATE Anton Nefedov
2017-08-04 15:27 ` Eric Blake
2017-08-01 14:19 ` [Qemu-devel] [PATCH v4 15/15] iotest 134: test cluster-misaligned encrypted write Anton Nefedov
2017-09-21 17:16 ` [Qemu-devel] [PATCH v4 00/15] qcow2: space preallocation and COW improvements Anton Nefedov
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=e47643b2-ff2e-ca38-e666-d89a28f0c46f@redhat.com \
--to=eblake@redhat.com \
--cc=anton.nefedov@virtuozzo.com \
--cc=den@virtuozzo.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).