From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Anton Nefedov <anton.nefedov@virtuozzo.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "qemu-block@nongnu.org" <qemu-block@nongnu.org>,
"kwolf@redhat.com" <kwolf@redhat.com>,
"mreitz@redhat.com" <mreitz@redhat.com>,
"eblake@redhat.com" <eblake@redhat.com>,
Denis Lunev <den@virtuozzo.com>,
"berto@igalia.com" <berto@igalia.com>
Subject: Re: [Qemu-devel] [PATCH v10 4/9] block: introduce BDRV_REQ_ALLOCATE flag
Date: Wed, 5 Dec 2018 12:59:17 +0000 [thread overview]
Message-ID: <f978f7f8-6d8c-968c-55c6-23c04818ef12@virtuozzo.com> (raw)
In-Reply-To: <20181203101429.88735-5-anton.nefedov@virtuozzo.com>
03.12.2018 13:14, 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 must return -ENOTSUP if allocation cannot
> be done efficiently.
> This has to be made sure of by both
> - the drivers that support the flag
> - and the common block layer (so it will not fall back to any slowpath
> (like writing zero buffers) in case the driver does not support
> the flag).
>
> Signed-off-by: Anton Nefedov <anton.nefedov@virtuozzo.com>
> Reviewed-by: Alberto Garcia <berto@igalia.com>
> ---
> include/block/block.h | 9 ++++++++-
> include/block/block_int.h | 2 +-
> block/io.c | 18 ++++++++++++++++--
> 3 files changed, 25 insertions(+), 4 deletions(-)
>
> diff --git a/include/block/block.h b/include/block/block.h
> index 7f5453b45b..f571082415 100644
> --- a/include/block/block.h
> +++ b/include/block/block.h
> @@ -83,8 +83,15 @@ typedef enum {
> */
> BDRV_REQ_SERIALISING = 0x80,
>
> + /* 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.
> + * If this flag is set then BDRV_REQ_ZERO_WRITE must also be set.
> + * This flag cannot be set together with BDRV_REQ_MAY_UNMAP.
and, may be, it can't be set with FUA too?
> + */
> + BDRV_REQ_ALLOCATE = 0x100,
> +
> /* Mask of valid flags */
> - BDRV_REQ_MASK = 0xff,
> + BDRV_REQ_MASK = 0x1ff,
> } BdrvRequestFlags;
>
> typedef struct BlockSizes {
> diff --git a/include/block/block_int.h b/include/block/block_int.h
> index f605622216..ff84c5d8aa 100644
> --- a/include/block/block_int.h
> +++ b/include/block/block_int.h
> @@ -724,7 +724,7 @@ struct BlockDriverState {
> * their children. */
> unsigned int supported_write_flags;
> /* Flags honored during pwrite_zeroes (so far: BDRV_REQ_FUA,
> - * BDRV_REQ_MAY_UNMAP, BDRV_REQ_WRITE_UNCHANGED) */
> + * BDRV_REQ_MAY_UNMAP, BDRV_REQ_WRITE_UNCHANGED, BDRV_REQ_ALLOCATE) */
> unsigned int supported_zero_flags;
>
> /* the following member gives a name to every node on the bs graph. */
> diff --git a/block/io.c b/block/io.c
> index bd9d688f8b..d9d7644858 100644
> --- a/block/io.c
> +++ b/block/io.c
> @@ -1534,7 +1534,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;
>
> @@ -1702,7 +1702,9 @@ static int coroutine_fn bdrv_aligned_pwritev(BdrvChild *child,
> !(flags & BDRV_REQ_ZERO_WRITE) && drv->bdrv_co_pwrite_zeroes &&
> qemu_iovec_is_zero(qiov)) {
> flags |= BDRV_REQ_ZERO_WRITE;
> - if (bs->detect_zeroes == BLOCKDEV_DETECT_ZEROES_OPTIONS_UNMAP) {
> + if (bs->detect_zeroes == BLOCKDEV_DETECT_ZEROES_OPTIONS_UNMAP &&
> + !(flags & BDRV_REQ_ALLOCATE))
dead check. we are in if (!(flags & BDRV_REQ_ZERO_WRITE)), so (flags & BDRV_REQ_ALLOCATE) must be zero as well.
> + {
> flags |= BDRV_REQ_MAY_UNMAP;
> }
> }
> @@ -1773,6 +1775,9 @@ static int coroutine_fn bdrv_co_do_zero_pwritev(BdrvChild *child,
>
> assert(flags & BDRV_REQ_ZERO_WRITE);
> if (head_padding_bytes || tail_padding_bytes) {
> + if (flags & BDRV_REQ_ALLOCATE) {
> + return -ENOTSUP;
> + }
> buf = qemu_blockalign(bs, align);
> iov = (struct iovec) {
> .iov_base = buf,
> @@ -1858,6 +1863,9 @@ int coroutine_fn bdrv_co_pwritev(BdrvChild *child,
> bool use_local_qiov = false;
> int ret;
>
> + assert(!((flags & BDRV_REQ_ALLOCATE) && (flags & BDRV_REQ_MAY_UNMAP)));
> + assert(!((flags & BDRV_REQ_ALLOCATE) && !(flags & BDRV_REQ_ZERO_WRITE)));
what about FUA?
> +
> trace_bdrv_co_pwritev(child->bs, offset, bytes, flags);
>
> if (!bs->drv) {
> @@ -1980,6 +1988,12 @@ int coroutine_fn bdrv_co_pwrite_zeroes(BdrvChild *child, int64_t offset,
> {
> trace_bdrv_co_pwrite_zeroes(child->bs, offset, bytes, flags);
>
> + if ((flags & BDRV_REQ_ALLOCATE) &&
> + !(child->bs->supported_zero_flags & BDRV_REQ_ALLOCATE))
> + {
> + return -ENOTSUP;
> + }
> +
> if (!(child->bs->open_flags & BDRV_O_UNMAP)) {
> flags &= ~BDRV_REQ_MAY_UNMAP;
> }
>
--
Best regards,
Vladimir
next prev parent reply other threads:[~2018-12-05 12:59 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 10:14 [Qemu-devel] [PATCH v10 0/9] qcow2: cluster space preallocation Anton Nefedov
2018-12-03 10:14 ` [Qemu-devel] [PATCH v10 1/9] mirror: inherit supported write/zero flags Anton Nefedov
2018-12-05 12:43 ` Vladimir Sementsov-Ogievskiy
2018-12-05 13:27 ` Anton Nefedov
2018-12-07 14:31 ` Alberto Garcia
2018-12-12 12:15 ` Vladimir Sementsov-Ogievskiy
2018-12-03 10:14 ` [Qemu-devel] [PATCH v10 2/9] blkverify: set " Anton Nefedov
2018-12-07 14:32 ` Alberto Garcia
2018-12-12 12:26 ` Vladimir Sementsov-Ogievskiy
2018-12-03 10:14 ` [Qemu-devel] [PATCH v10 3/9] quorum: set supported write flags Anton Nefedov
2018-12-07 14:33 ` Alberto Garcia
2018-12-07 14:46 ` Anton Nefedov
2018-12-07 14:54 ` Alberto Garcia
2018-12-12 12:33 ` Vladimir Sementsov-Ogievskiy
2018-12-03 10:14 ` [Qemu-devel] [PATCH v10 4/9] block: introduce BDRV_REQ_ALLOCATE flag Anton Nefedov
2018-12-05 12:59 ` Vladimir Sementsov-Ogievskiy [this message]
2018-12-05 13:38 ` Anton Nefedov
2018-12-03 10:14 ` [Qemu-devel] [PATCH v10 5/9] block: treat BDRV_REQ_ALLOCATE as serialising Anton Nefedov
2018-12-05 13:14 ` Vladimir Sementsov-Ogievskiy
2018-12-05 14:01 ` Anton Nefedov
2018-12-12 12:48 ` Vladimir Sementsov-Ogievskiy
2018-12-13 11:57 ` Anton Nefedov
2018-12-03 10:14 ` [Qemu-devel] [PATCH v10 6/9] file-posix: support BDRV_REQ_ALLOCATE Anton Nefedov
2018-12-05 13:25 ` Vladimir Sementsov-Ogievskiy
2018-12-05 14:11 ` Anton Nefedov
2018-12-12 17:19 ` Vladimir Sementsov-Ogievskiy
2018-12-13 12:01 ` Anton Nefedov
2018-12-07 15:09 ` Alberto Garcia
2018-12-03 10:14 ` [Qemu-devel] [PATCH v10 8/9] qcow2: skip writing zero buffers to empty COW areas Anton Nefedov
2018-12-03 13:59 ` Alberto Garcia
2018-12-03 14:04 ` Anton Nefedov
2018-12-05 14:01 ` Vladimir Sementsov-Ogievskiy
2018-12-05 16:59 ` Anton Nefedov
2018-12-05 17:42 ` Vladimir Sementsov-Ogievskiy
2018-12-13 12:02 ` Vladimir Sementsov-Ogievskiy
2018-12-13 13:57 ` Anton Nefedov
2018-12-14 16:20 ` Vladimir Sementsov-Ogievskiy
2018-12-17 10:17 ` Anton Nefedov
2018-12-03 10:14 ` [Qemu-devel] [PATCH v10 7/9] block: support BDRV_REQ_ALLOCATE in passthrough drivers Anton Nefedov
2018-12-05 13:28 ` Vladimir Sementsov-Ogievskiy
2018-12-07 15:00 ` Alberto Garcia
2018-12-03 10:15 ` [Qemu-devel] [PATCH v10 9/9] iotest 134: test cluster-misaligned encrypted write 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=f978f7f8-6d8c-968c-55c6-23c04818ef12@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=anton.nefedov@virtuozzo.com \
--cc=berto@igalia.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).