qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] Re: [PATCH v6 0/5] qed: Add QEMU Enhanced Disk format
Date: Fri, 17 Dec 2010 13:22:10 +0000	[thread overview]
Message-ID: <20101217132210.GA25008@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <4D0B60C0.5070109@redhat.com>

On Fri, Dec 17, 2010 at 02:08:16PM +0100, Kevin Wolf wrote:
> Am 06.12.2010 17:07, schrieb Stefan Hajnoczi:
> > For a changelog against v5, see below.
> > 
> > QEMU Enhanced Disk format is a disk image format that forgoes features
> > found in qcow2 in favor of better levels of performance and data
> > integrity.  Due to its simpler on-disk layout, it is possible to safely
> > perform metadata updates more efficiently.
> > 
> > Installations, suspend-to-disk, and other allocation-heavy I/O workloads
> > will see increased performance due to fewer I/Os and syncs.  Workloads
> > that do not cause new clusters to be allocated will perform similar to
> > raw images due to in-memory metadata caching.
> > 
> > The format supports sparse disk images.  It does not rely on the host
> > filesystem holes feature, making it a good choice for sparse disk images
> > that need to be transferred over channels where holes are not supported.
> > 
> > Backing files are supported so only deltas against a base image can be
> > stored.  The base image may be smaller than the image file.
> > 
> > The file format is extensible so that additional features can be added
> > later with graceful compatibility handling.  A specification for the file
> > format is included in this patchset.
> > 
> > Internal snapshots are not supported.  This eliminates the need for
> > additional metadata to track copy-on-write clusters.
> > 
> > Compression and encryption are not supported.  They add complexity and can be
> > implemented at other layers in the stack (i.e. inside the guest or on the
> > host).  Encryption has been identified as a potential future extension and the
> > file format allows for this.
> > 
> > Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
> > Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
> 
> Thanks, reluctantly applied to the block branch. ;-)

Thank you Kevin!

Stefan

      reply	other threads:[~2010-12-17 13:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06 16:07 [Qemu-devel] [PATCH v6 0/5] qed: Add QEMU Enhanced Disk format Stefan Hajnoczi
2010-12-06 16:07 ` [Qemu-devel] [PATCH v6 1/5] docs: Add QED image format specification Stefan Hajnoczi
2010-12-06 16:08 ` [Qemu-devel] [PATCH v6 2/5] qed: Add QEMU Enhanced Disk image format Stefan Hajnoczi
2010-12-06 16:08 ` [Qemu-devel] [PATCH v6 3/5] qed: Table, L2 cache, and cluster functions Stefan Hajnoczi
2010-12-06 16:08 ` [Qemu-devel] [PATCH v6 4/5] qed: Read/write support Stefan Hajnoczi
2010-12-06 16:08 ` [Qemu-devel] [PATCH v6 5/5] qed: Consistency check support Stefan Hajnoczi
2010-12-17 13:08 ` [Qemu-devel] Re: [PATCH v6 0/5] qed: Add QEMU Enhanced Disk format Kevin Wolf
2010-12-17 13:22   ` Stefan Hajnoczi [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=20101217132210.GA25008@stefanha-thinkpad.localdomain \
    --to=stefanha@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=kwolf@redhat.com \
    --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).