From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:60208) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SeSop-0006yt-IT for qemu-devel@nongnu.org; Tue, 12 Jun 2012 11:15:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SeSoi-0003GG-0w for qemu-devel@nongnu.org; Tue, 12 Jun 2012 11:15:43 -0400 Received: from mx1.redhat.com ([209.132.183.28]:26193) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SeSoh-0003Fe-Pn for qemu-devel@nongnu.org; Tue, 12 Jun 2012 11:15:35 -0400 Message-ID: <4FD75D11.60600@redhat.com> Date: Tue, 12 Jun 2012 17:15:29 +0200 From: Kevin Wolf MIME-Version: 1.0 References: <1339513546-17538-1-git-send-email-stefanha@linux.vnet.ibm.com> In-Reply-To: <1339513546-17538-1-git-send-email-stefanha@linux.vnet.ibm.com> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] qemu-img: document qed format on qemu-img man page List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Michael Tokarev , qemu-devel@nongnu.org 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 > Signed-off-by: Stefan Hajnoczi > --- > 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