From: Max Reitz <mreitz@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] block: Trivial fixes in offloading code
Date: Wed, 4 Jul 2018 16:09:04 +0200 [thread overview]
Message-ID: <d9d73f8e-89c8-4ae9-c6b6-a180826768bd@redhat.com> (raw)
In-Reply-To: <20180703012626.GB485@lemon.usersys.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1453 bytes --]
On 2018-07-03 03:26, Fam Zheng wrote:
> On Mon, 07/02 14:35, Max Reitz wrote:
>> On 2018-07-02 04:58, Fam Zheng wrote:
>>> These are the low priority ones spotted by Kevin and Max last week.
>>>
>>> Fam Zheng (4):
>>> qcow2: Drop unused cluster_data
>>> file-posix: Fix fd_open check in raw_co_copy_range_to
>>> qcow2: Drop unreachable break
>>> raw: Drop superfluous semicolon
>>>
>>> block/file-posix.c | 2 +-
>>> block/qcow2.c | 3 ---
>>> block/raw-format.c | 2 +-
>>> 3 files changed, 2 insertions(+), 5 deletions(-)
>>
>> Thanks, applied to my block branch:
>>
>> https://git.xanclic.moe/XanClic/qemu/commits/branch/block
>>
>>
>> Do you want to make qcow2_co_copy_range_to() do something special on
>> BDRV_REQ_ZERO_WRITE? To me, it seems natural, but on the other hand
>> maybe it wouldn't bring anything. If the protocol layer supports copy
>> offloading, then it'll probably do that zero write efficiently anyway.
>> If it doesn't, qemu-img convert will just fall back to the usual
>> implementation which involves writing zeroes when zeroes are read, so...
>> What's your opinion?
>
> In bdrv_co_copy_range_internal() there is
>
> if (flags & BDRV_REQ_ZERO_WRITE) {
> return bdrv_co_pwrite_zeroes(dst, dst_offset, bytes, flags);
> }
>
> before calling driver .bdrv_co_copy_range_to() callback. I think this is enough?
Ah, right... Yep, that's enough. :-)
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-07-04 14:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 2:58 [Qemu-devel] [PATCH 0/4] block: Trivial fixes in offloading code Fam Zheng
2018-07-02 2:58 ` [Qemu-devel] [PATCH 1/4] qcow2: Drop unused cluster_data Fam Zheng
2018-07-02 2:58 ` [Qemu-devel] [PATCH 2/4] file-posix: Fix fd_open check in raw_co_copy_range_to Fam Zheng
2018-07-02 2:58 ` [Qemu-devel] [PATCH 3/4] qcow2: Drop unreachable break Fam Zheng
2018-07-02 2:58 ` [Qemu-devel] [PATCH 4/4] raw: Drop superfluous semicolon Fam Zheng
2018-07-02 12:35 ` [Qemu-devel] [PATCH 0/4] block: Trivial fixes in offloading code Max Reitz
2018-07-03 1:26 ` Fam Zheng
2018-07-04 14:09 ` Max Reitz [this message]
2018-07-02 15:19 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
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=d9d73f8e-89c8-4ae9-c6b6-a180826768bd@redhat.com \
--to=mreitz@redhat.com \
--cc=famz@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).