From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] qed: Add support for zero clusters
Date: Mon, 11 Apr 2011 12:45:08 +0200 [thread overview]
Message-ID: <4DA2DBB4.1040507@redhat.com> (raw)
In-Reply-To: <1292601502-5222-1-git-send-email-stefanha@linux.vnet.ibm.com>
Am 17.12.2010 16:58, schrieb Stefan Hajnoczi:
> This patch series adds zero data clusters to QED. Clusters can be marked as
> zero clusters to store zeroed regions in a space-efficient way. The patch
> never actually creates new zero clusters but includes the I/O path support code
> to handle them if they are used by an image file.
>
> Image streaming and copy-on-read take advantage of zero data clusters to avoid
> expanding out zeroes from the backing file. Those features are separate
> patches that will come later but I'm presenting this patch now so we can get
> this core QED image format feature in before doing the first QEMU release
> containing QED.
>
> The first patch fixes up an issue with the QED merge where '^' characters were
> dropped from the QED specification.
>
> The last two patches document and implement zero clusters, which were
> originally implemented by Anthony Liguori <aliguori@us.ibm.com>.
Thanks, applied all to the block branch.
Kevin
prev parent reply other threads:[~2011-04-11 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 15:58 [Qemu-devel] [PATCH 0/3] qed: Add support for zero clusters Stefan Hajnoczi
2010-12-17 15:58 ` [Qemu-devel] [PATCH 1/3] docs: Fix missing carets in QED specification Stefan Hajnoczi
2010-12-17 15:58 ` [Qemu-devel] [PATCH 2/3] docs: Describe zero data clusters " Stefan Hajnoczi
2010-12-17 15:58 ` [Qemu-devel] [PATCH 3/3] qed: Add support for zero clusters Stefan Hajnoczi
2011-04-11 10:45 ` Kevin Wolf [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=4DA2DBB4.1040507@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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 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).