From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [5839] qemu-img: open files with cache=writeback
Date: Mon, 1 Dec 2008 00:47:06 +0100 [thread overview]
Message-ID: <20081130234706.GA29460@hall.aurel32.net> (raw)
In-Reply-To: <49331A17.2080707@codemonkey.ws>
On Sun, Nov 30, 2008 at 04:56:23PM -0600, Anthony Liguori wrote:
> Aurelien Jarno wrote:
> >Revision: 5839
> > http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5839
> >Author: aurel32
> >Date: 2008-11-30 19:12:49 +0000 (Sun, 30 Nov 2008)
> >
> >Log Message:
> >-----------
> >qemu-img: open files with cache=writeback
> >
> >Data integrity is not important in qemu-img, so open the files with
> >cache=writeback. This fixes the performance regression seen with qemu-img
> >since revision 5485, and most particularly with the qcow2 format.
> >
> >Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
> >
>
> My thinking was to just make qcow2 always default to cache=writeback. I
> posted an RFC but received no feedback. I guess that means noone
> disagreed :-)
>
Sorry if I haven't answered to your RFC, but as you said no complains
means the patch is ok. I think you can commit it.
I have tried your patch to solve the problem, but it was not fixing all
the problems: other formats are also affected by the slowdown, as the
I/O operations in qemu-img are very different than in qemu.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
prev parent reply other threads:[~2008-11-30 23:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-30 19:12 [Qemu-devel] [5839] qemu-img: open files with cache=writeback Aurelien Jarno
2008-11-30 22:56 ` Anthony Liguori
2008-11-30 23:47 ` Aurelien Jarno [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=20081130234706.GA29460@hall.aurel32.net \
--to=aurelien@aurel32.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.