From: Stefan Hajnoczi <stefanha@gmail.com>
To: Fam Zheng <famz@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
Feiran Zheng <feiran.zheng@emc.com>
Subject: Re: [Qemu-devel] [PATCH 5/5] vmdk: add bdrv_co_write_zeroes
Date: Fri, 19 Apr 2013 11:12:55 +0200 [thread overview]
Message-ID: <20130419091255.GD28732@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1366343325-5252-6-git-send-email-famz@redhat.com>
On Fri, Apr 19, 2013 at 11:48:45AM +0800, Fam Zheng wrote:
> From: Feiran Zheng <feiran.zheng@emc.com>
>
> Use special offset to write zeroes efficiently, when zeroed-grain GTE is
> available. If zero-write an allocated cluster, cluster is leaked because
> its offset pointer is overwritten by "0x1".
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> block/vmdk.c | 63 +++++++++++++++++++++++++++++++++++++++++++++++-------------
> 1 file changed, 50 insertions(+), 13 deletions(-)
Do existing qemu-iotests zero write tests cases cover this? Do you need
to add vmdk to their list of supported formats?
Stefan
next prev parent reply other threads:[~2013-04-19 9:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 3:48 [Qemu-devel] [PATCH 0/5] vmdk: zeroed-grain GTE support Fam Zheng
2013-04-19 3:48 ` [Qemu-devel] [PATCH 1/5] vmdk: named return code Fam Zheng
2013-04-19 3:48 ` [Qemu-devel] [PATCH 2/5] vmdk: add support for “zeroed‐grain” GTE Fam Zheng
2013-04-19 8:59 ` Stefan Hajnoczi
2013-04-19 9:10 ` Fam Zheng
2013-04-19 11:22 ` Stefan Hajnoczi
2013-04-19 3:48 ` [Qemu-devel] [PATCH 3/5] vmdk: Add option to create zeroed-grain image Fam Zheng
2013-04-19 9:05 ` Stefan Hajnoczi
2013-04-19 3:48 ` [Qemu-devel] [PATCH 4/5] vmdk: change magic number to macro Fam Zheng
2013-04-19 9:06 ` Stefan Hajnoczi
2013-04-19 3:48 ` [Qemu-devel] [PATCH 5/5] vmdk: add bdrv_co_write_zeroes Fam Zheng
2013-04-19 9:12 ` Stefan Hajnoczi [this message]
2013-04-19 11:04 ` 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=20130419091255.GD28732@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=famz@redhat.com \
--cc=feiran.zheng@emc.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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.