From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] block: Document BDRV_REQ_WRITE_UNCHANGED support
Date: Wed, 9 May 2018 22:10:18 +0200 [thread overview]
Message-ID: <8efe25d9-c89e-9582-e2a0-57812441556e@redhat.com> (raw)
In-Reply-To: <20180502140359.18222-1-mreitz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
On 2018-05-02 16:03, Max Reitz wrote:
> Add BDRV_REQ_WRITE_UNCHANGED to the list of flags honored during pwrite
> and pwrite_zeroes, and also add a note on when you absolutely need to
> support it.
>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> I did not include a note on how this might be useful to protocol
> drivers, because BDRV_REQ_WRITE_UNCHANGED requests will usually not end
> up on the protocol level anyway.
> (I suppose it would be possible in theory if a protocol driver reports a
> certain range as unallocated and the user installs a copy-on-read
> driver on top, but I think every protocol driver currently reports
> everything as allocated.)
> ---
> include/block/block_int.h | 18 ++++++++++++++++--
> 1 file changed, 16 insertions(+), 2 deletions(-)
Thanks for the review, applied to my block branch.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-05-09 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 14:03 [Qemu-devel] [PATCH] block: Document BDRV_REQ_WRITE_UNCHANGED support Max Reitz
2018-05-02 14:15 ` Eric Blake
2018-05-09 20:10 ` Max Reitz [this message]
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=8efe25d9-c89e-9582-e2a0-57812441556e@redhat.com \
--to=mreitz@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@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).