From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>, Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Jeff Cody <jcody@redhat.com>,
qemu-stable@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
jsnow@redhat.com, wangxiaolong@ucloud.cn
Subject: Re: [Qemu-devel] [PATCH v4 3/8] mirror: Do zero write on target if sectors not allocated
Date: Mon, 25 May 2015 16:38:28 +0200 [thread overview]
Message-ID: <556333E4.3020602@redhat.com> (raw)
In-Reply-To: <555F8FA5.9050209@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 22/05/2015 22:20, Eric Blake wrote:
> But I'm worried about a shallow copy. If I start with "base <-
> active", where "active" has an explicit zero cluster that is
> overwriting an allocated non-zero cluster in "base", and I'm
> creating the shallow clone to "base <- copy", then the default of
> 'unmap=true' says that bdrv_aio_write_zeroes() may attempt to unmap
> the cluster in "copy". At which point, doesn't that mean that
> reading from "copy" will dredge up the non-zero data from "base",
> which is NOT a faithful mirroring of "active"?
No, bdv_aio_write_zeroes+BDRV_REQ_MAY_UNMAP only unmaps if it results
in zeroes. In addition, unlike bdrv_aio_discard,
bdrv_aio_write_zeroes will do a real write of zeroes if [sector_num,
sector_num+nb_sectors) is not aligned to the disk's unmap granularity.
Paolo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJVYzPhAAoJEL/70l94x66DGMYIAKKGQIts+Ve689Iar0P6TmXz
BOO0xKJm477PAP9pvUtnGnpt+g2+OqKp0VBTu4F3tbLIQLQOZT1kAZ9oxJ9PMnEa
69c8n86DWdJIgx1lcnOI2wgjaoG65e2K2MH3vYs2Rj6ZD65/FfsF7+oj/R9zCgZm
MIMSiW/fbC5EjBQxOTkDWekuB+/iNRtV9K8YBCtmb8ZlF28X3FPrdZnoqcZGtxPL
RoGYLckjEuLMLSsDH3Frb1+lfKpCaSlJ203ihQQfXzr/8UBH4zOqPZOTbrhdA1pZ
3fHaW5KWyZ1vjW6bb64kpjMnRwCRxB+uAAY4pUmUCZxGsHxh19hGUeSuOexFvqc=
=GUVR
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-05-25 14:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 3:40 [Qemu-devel] [PATCH v4 0/8] block: Mirror discarded sectors Fam Zheng
2015-05-22 3:40 ` [Qemu-devel] [PATCH v4 1/8] block: Add "base" option to bdrv_get_block_status Fam Zheng
2015-05-22 19:32 ` Eric Blake
2015-05-25 14:43 ` Paolo Bonzini
2015-05-26 3:30 ` Fam Zheng
2015-05-22 3:40 ` [Qemu-devel] [PATCH v4 2/8] qmp: Add optional bool "unmap" to drive-mirror Fam Zheng
2015-05-22 19:57 ` Eric Blake
2015-05-22 3:40 ` [Qemu-devel] [PATCH v4 3/8] mirror: Do zero write on target if sectors not allocated Fam Zheng
2015-05-22 20:20 ` Eric Blake
2015-05-25 14:38 ` Paolo Bonzini [this message]
2015-05-25 14:36 ` Paolo Bonzini
2015-05-25 14:41 ` Paolo Bonzini
2015-05-22 3:40 ` [Qemu-devel] [PATCH v4 4/8] block: Fix dirty bitmap in bdrv_co_discard Fam Zheng
2015-05-22 20:22 ` Eric Blake
2015-05-22 3:40 ` [Qemu-devel] [PATCH v4 5/8] block: Remove bdrv_reset_dirty Fam Zheng
2015-05-22 3:40 ` [Qemu-devel] [PATCH v4 6/8] qemu-iotests: Make block job methods common Fam Zheng
2015-05-22 3:40 ` [Qemu-devel] [PATCH v4 7/8] qemu-iotests: Add test case for mirror with unmap Fam Zheng
2015-05-22 3:41 ` [Qemu-devel] [PATCH v4 8/8] iotests: Use event_wait in wait_ready Fam Zheng
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=556333E4.3020602@redhat.com \
--to=pbonzini@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wangxiaolong@ucloud.cn \
/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).