From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-img: document qed format on qemu-img man page
Date: Tue, 12 Jun 2012 17:15:29 +0200 [thread overview]
Message-ID: <4FD75D11.60600@redhat.com> (raw)
In-Reply-To: <1339513546-17538-1-git-send-email-stefanha@linux.vnet.ibm.com>
Am 12.06.2012 17:05, schrieb Stefan Hajnoczi:
> The qemu-img.1 man page is missing the qed format from its list of
> supported formats. Document the image creation options for qed.
>
> Suggested-by: Michael Tokarev <mjt@tls.msk.ru>
> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
> ---
> When the qcow2 QED mode is merged we can update this again to reflect good
> cache=writethrough performance in qcow2v3 /w QED mode.
>
> qemu-img.texi | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/qemu-img.texi b/qemu-img.texi
> index 6fc3c28..78640a9 100644
> --- a/qemu-img.texi
> +++ b/qemu-img.texi
> @@ -232,6 +232,28 @@ to grow.
>
> @end table
>
> +@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.
Can we restrict this clearly to cache=writethrough only and possibly add
a few words about QED's future?
It's good to have the option today for the few people that actually need
cache=writethrough, but I don't want more people than necessary to use
it only to notice after a while that there's no more active development
of QED and they have to do a painful conversion of all their images.
Kevin
next prev parent reply other threads:[~2012-06-12 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 15:05 [Qemu-devel] [PATCH] qemu-img: document qed format on qemu-img man page Stefan Hajnoczi
2012-06-12 15:15 ` Kevin Wolf [this message]
2012-06-13 8:19 ` 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=4FD75D11.60600@redhat.com \
--to=kwolf@redhat.com \
--cc=mjt@tls.msk.ru \
--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).