qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anton Nefedov <anton.nefedov@virtuozzo.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, kwolf@redhat.com, mreitz@redhat.com,
	eblake@redhat.com, den@virtuozzo.com, berto@igalia.com
Subject: Re: [Qemu-devel] [PATCH v8 6/9] file-posix: support BDRV_REQ_ALLOCATE
Date: Fri, 16 Mar 2018 17:53:29 +0300	[thread overview]
Message-ID: <2157719f-a2cb-1646-df75-a9aeb9f06d8d@virtuozzo.com> (raw)
In-Reply-To: <1520849818-6915-7-git-send-email-anton.nefedov@virtuozzo.com>



On 12/3/2018 1:16 PM, Anton Nefedov wrote:
> Current write_zeroes implementation is good enough to satisfy this flag too
> 
> Signed-off-by: Anton Nefedov <anton.nefedov@virtuozzo.com>
> Reviewed-by: Alberto Garcia <berto@igalia.com>
> Reviewed-by: Max Reitz <mreitz@redhat.com>

strictly speaking this patch differs from v8 as well
(rebase required an extra change, see below)
so perhaps I should have stripped the review tags too

> ---
>   block/file-posix.c | 10 +++++++++-
>   1 file changed, 9 insertions(+), 1 deletion(-)
> 
> diff --git a/block/file-posix.c b/block/file-posix.c
> index 7f2cc63..2136df9 100644
> --- a/block/file-posix.c
> +++ b/block/file-posix.c
> @@ -560,7 +560,10 @@ static int raw_open_common(BlockDriverState *bs, QDict *options,
>       }
>       if (S_ISREG(st.st_mode)) {
>           s->discard_zeroes = true;
> +#ifdef CONFIG_FALLOCATE
>           s->has_fallocate = true;
> +        bs->supported_zero_flags |= BDRV_REQ_ALLOCATE;
> +#endif
>       }
>       if (S_ISBLK(st.st_mode)) {
>   #ifdef BLKDISCARDZEROES
> @@ -595,10 +598,11 @@ static int raw_open_common(BlockDriverState *bs, QDict *options,
>   #ifdef CONFIG_XFS
>       if (platform_test_xfs_fd(s->fd)) {
>           s->is_xfs = true;
> +        bs->supported_zero_flags |= BDRV_REQ_ALLOCATE;
>       }
>   #endif
>   
> -    bs->supported_zero_flags = s->discard_zeroes ? BDRV_REQ_MAY_UNMAP : 0;
> +    bs->supported_zero_flags |= s->discard_zeroes ? BDRV_REQ_MAY_UNMAP : 0;
>       ret = 0;

(this change is new in v9)

>   fail:
>       if (filename && (bdrv_flags & BDRV_O_TEMPORARY)) {
> @@ -1416,6 +1420,10 @@ static ssize_t handle_aiocb_write_zeroes(RawPosixAIOData *aiocb)
>           }
>           s->has_fallocate = false;
>       }
> +
> +    if (!s->has_fallocate) {
> +        aiocb->bs->supported_zero_flags &= ~BDRV_REQ_ALLOCATE;
> +    }
>   #endif
>   
>       return -ENOTSUP;
> 

  reply	other threads:[~2018-03-16 14:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 10:16 [Qemu-devel] [PATCH v8 0/9] qcow2: cluster space preallocation Anton Nefedov
2018-03-12 10:16 ` [Qemu-devel] [PATCH v8 1/9] mirror: inherit supported write/zero flags Anton Nefedov
2018-03-16 10:35   ` Alberto Garcia
2018-03-12 10:16 ` [Qemu-devel] [PATCH v8 2/9] blkverify: set " Anton Nefedov
2018-03-12 10:16 ` [Qemu-devel] [PATCH v8 3/9] quorum: " Anton Nefedov
2018-03-16 10:39   ` Alberto Garcia
2018-03-12 10:16 ` [Qemu-devel] [PATCH v8 4/9] block: introduce BDRV_REQ_ALLOCATE flag Anton Nefedov
2018-03-16 11:01   ` Alberto Garcia
2018-03-16 14:52     ` Anton Nefedov
2018-03-12 10:16 ` [Qemu-devel] [PATCH v8 5/9] block: treat BDRV_REQ_ALLOCATE as serialising Anton Nefedov
2018-03-19 11:02   ` Alberto Garcia
2018-03-12 10:16 ` [Qemu-devel] [PATCH v8 6/9] file-posix: support BDRV_REQ_ALLOCATE Anton Nefedov
2018-03-16 14:53   ` Anton Nefedov [this message]
2018-03-12 10:16 ` [Qemu-devel] [PATCH v8 7/9] block: support BDRV_REQ_ALLOCATE in passthrough drivers Anton Nefedov
2018-03-16 11:03   ` Alberto Garcia
2018-03-12 10:16 ` [Qemu-devel] [PATCH v8 8/9] qcow2: skip writing zero buffers to empty COW areas Anton Nefedov
2018-03-16 13:58   ` Alberto Garcia
2018-03-16 15:09     ` Anton Nefedov
2018-03-12 10:16 ` [Qemu-devel] [PATCH v8 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=2157719f-a2cb-1646-df75-a9aeb9f06d8d@virtuozzo.com \
    --to=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).