From: wyang <w90p710@gmail.com>
To: Eric Blake <eblake@redhat.com>, Vasiliy Tolstov <v.tolstov@selfip.ru>
Cc: jcody@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block/mirror: enable detect zeroes when driving mirror
Date: Wed, 23 Nov 2016 11:14:57 +0800 [thread overview]
Message-ID: <583509B1.6030400@gmail.com> (raw)
In-Reply-To: <c41abc51-fce9-b4fc-4366-a72008655284@redhat.com>
On 2016年11月22日 21:44, Eric Blake wrote:
> On 11/21/2016 08:31 PM, wyang wrote:
>> On 2016年11月21日 14:51, Vasiliy Tolstov wrote:
>>> 21 Ноя 2016 г. 4:27 пользователь "Yang Wei" <w90p710@gmail.com
>>> <mailto:w90p710@gmail.com>> написал:
>>>> In order to preserve sparse disk image, detect_zeroes
>>>> should also be enabled when bdrv_get_block_status_above()
>>>> returns BDRV_BLOCK_DATA
>>>>
>>>> Signed-off-by: Yang Wei <w90p710@gmail.com <mailto:w90p710@gmail.com>>
>>>> ---
>>> Hi, does this patch fixes bug
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1219541 ? Or it unrelated
>>> to this issue?
>>>
>> yes, you also need to backport the functionality of NBD's write
>> zeroes( fa778f and 1f4d6d)
> And also my posted (but not yet applied) patch:
> nbd: Allow unmap and fua during write zeroes
> https://lists.gnu.org/archive/html/qemu-devel/2016-11/msg03496.html
Got it, I would also backport it to my qemu repo. thank you Eric.;-)
Wei
>
next prev parent reply other threads:[~2016-11-23 3:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 1:24 [Qemu-devel] [PATCH] block/mirror: enable detect zeroes when driving mirror Yang Wei
2016-11-21 1:34 ` no-reply
2016-11-21 6:51 ` Vasiliy Tolstov
2016-11-22 2:31 ` wyang
2016-11-22 13:44 ` Eric Blake
2016-11-23 3:14 ` wyang [this message]
2016-11-21 11:34 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2016-11-22 3:45 ` wyang
2016-11-22 10:09 ` Kevin Wolf
2016-11-23 3:12 ` wyang
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=583509B1.6030400@gmail.com \
--to=w90p710@gmail.com \
--cc=eblake@redhat.com \
--cc=jcody@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=v.tolstov@selfip.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.