From: Anton Nefedov <anton.nefedov@virtuozzo.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@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 5/9] block: treat BDRV_REQ_ALLOCATE as serialising
Date: Thu, 13 Dec 2018 11:57:36 +0000 [thread overview]
Message-ID: <ef59f2ba-f59d-aed4-2c3b-af75d9e2df6b@virtuozzo.com> (raw)
In-Reply-To: <bd2c4805-86b4-469a-6e3f-01f787d4b3a9@virtuozzo.com>
On 12/12/2018 3:48 PM, Vladimir Sementsov-Ogievskiy wrote:
> 05.12.2018 17:01, Anton Nefedov wrote:
>> --- a/include/block/block.h
>> +++ b/include/block/block.h
>> @@ -87,6 +87,9 @@ typedef enum {
>> * 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.
>> + * This flag implicitly behaves as BDRV_REQ_SERIALISING i.e. it is
>> + * protected from conflicts with overlapping requests. If such
>> conflict is
>> + * detected, -EAGAIN is returned.
>
> "behaves as" sounds like "do the same" for me, so better is "implicitly sets" or something like this.
>
"implicitly sets" is good enough for me
next prev parent reply other threads:[~2018-12-13 11:57 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 [this message]
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=ef59f2ba-f59d-aed4-2c3b-af75d9e2df6b@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 \
--cc=vsementsov@virtuozzo.com \
/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).