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 6/9] file-posix: support BDRV_REQ_ALLOCATE
Date: Wed, 12 Dec 2018 17:19:21 +0000 [thread overview]
Message-ID: <312f075e-6e7f-5e8b-e7c9-e0d4c94e5ede@virtuozzo.com> (raw)
In-Reply-To: <ba2723a2-fd5d-6e96-002f-70c14092ded8@virtuozzo.com>
05.12.2018 17:11, Anton Nefedov wrote:
> On 5/12/2018 4:25 PM, Vladimir Sementsov-Ogievskiy wrote:
>> 03.12.2018 13:14, Anton Nefedov wrote:
>>> Current write_zeroes implementation is good enough to satisfy this flag too
>>>
>>> Signed-off-by: Anton Nefedov <anton.nefedov@virtuozzo.com>
>>> ---
>>> block/file-posix.c | 8 +++++++-
>>> 1 file changed, 7 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/block/file-posix.c b/block/file-posix.c
>>> index 07bbdab953..b0b7ab0159 100644
>>> --- a/block/file-posix.c
>>> +++ b/block/file-posix.c
>>> @@ -603,6 +603,7 @@ static int raw_open_common(BlockDriverState *bs, QDict *options,
>>> } else {
>>> s->discard_zeroes = true;
>>> s->has_fallocate = true;
>>> + bs->supported_zero_flags = BDRV_REQ_ALLOCATE;
>>> }
>>> } else {
>>> if (!(S_ISCHR(st.st_mode) || S_ISBLK(st.st_mode))) {
>>> @@ -646,10 +647,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;
>>
>> why we should handle xfs separately? is there a case with xfs, not handled by previous generic if ()?
>>
>
> The driver supports ALLOCATE either when it's XFS, or when fallocate is
> available. Currently there is no test for fallocate, it's just implied
> it's supported until ENOTSUP returned.
> I think it's safer (for possible future changes) to set it twice even
> though you're right and first condition currently covers the XFS
> condition too.
Aha, ok.
>
>>> }
>>> #endif
>>>
>>> - bs->supported_zero_flags = BDRV_REQ_MAY_UNMAP;
>>> + bs->supported_zero_flags |= BDRV_REQ_MAY_UNMAP;
>>> ret = 0;
>>> fail:
>>> if (filename && (bdrv_flags & BDRV_O_TEMPORARY)) {
>>> @@ -1520,6 +1522,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;
>>> + }
hm, if CONFIG_FALLOCATE is disabled, flag will remain in supported_zero_flags
>>> #endif
>>>
>>> return -ENOTSUP;
>>>
>>
>>
--
Best regards,
Vladimir
next prev parent reply other threads:[~2018-12-12 17:19 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
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 [this message]
2018-12-13 12:01 ` Anton Nefedov
2018-12-07 15:09 ` Alberto Garcia
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: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: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=312f075e-6e7f-5e8b-e7c9-e0d4c94e5ede@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).