From: Stefan Hajnoczi <stefanha@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] Documentation: Update image format information
Date: Wed, 21 Nov 2012 16:14:08 +0100 [thread overview]
Message-ID: <20121121151408.GB22778@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1353504237-5608-3-git-send-email-kwolf@redhat.com>
On Wed, Nov 21, 2012 at 02:23:57PM +0100, Kevin Wolf wrote:
> @item qed
> -Image format with support for backing files and compact image files (when your
> -filesystem or transport medium does not support holes). Good performance due
> -to less metadata than the more featureful qcow2 format, especially with
> -cache=writethrough or cache=directsync. Consider using qcow2 which will soon
> -have a similar optimization and is most actively developed.
> +Old QEMU image format. Left for compatibility.
> +
> +For new images, use qcow2 instead. You might want to consider using the
> +@code{lazy_refcounts=on} option to get a more QED-like behaviour.
The first sentence should be kept, it describes the general feature set
and scope of this image format. I agree that the rest of the paragraph
can be dropped.
You could insert a statement saying that qcow2 is now preferred because
it is actively developed and offers advanced features and performance as
the very first sentence.
Stefan
next prev parent reply other threads:[~2012-11-21 15:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 13:23 [Qemu-devel] [PATCH 1.3 0/2] Manpage updates for 1.3 Kevin Wolf
2012-11-21 13:23 ` [Qemu-devel] [PATCH 1/2] Documentation: Update block cache mode information Kevin Wolf
2012-11-21 13:36 ` Peter Maydell
2012-11-21 14:41 ` [Qemu-devel] [PATCH v2 " Kevin Wolf
2012-11-21 13:23 ` [Qemu-devel] [PATCH 2/2] Documentation: Update image format information Kevin Wolf
2012-11-21 15:14 ` Stefan Hajnoczi [this message]
2012-11-21 15:22 ` Kevin Wolf
2012-11-22 7:37 ` Stefan Hajnoczi
2012-11-22 9:08 ` Kevin Wolf
2012-11-22 11:59 ` Stefan Hajnoczi
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=20121121151408.GB22778@stefanha-thinkpad.redhat.com \
--to=stefanha@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).