From: Michael Tokarev <mjt@tls.msk.ru>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
avi@redhat.com, qemu-devel@nongnu.org, hch@lst.de
Subject: [Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"
Date: Tue, 24 Aug 2010 15:06:51 +0400 [thread overview]
Message-ID: <4C73A7CB.5000707@msgid.tls.msk.ru> (raw)
In-Reply-To: <AANLkTimYQHv15jprqpa8ubTQMR=bnisDB4SposC07tZw@mail.gmail.com>
24.08.2010 15:02, Stefan Hajnoczi wrote:
[]
> Sometimes an improvement has a side effect and it makes sense to hold
> back the improvement until the side effect can be resolved. The
> period of time in which users could rely on qcow2 data integrity is
> small to none, I feel reverting the commit makes sense.
And I agree with this.
> QEMU 0.12.5 has qcow2 sync metadata writes in commit
> 37060c28e522843fbf6f7e59af745dfcb05b132c. Was the performance
> regression spotted on 0.12.5 or 0.13?
It started as a debian bugreport ( http://bugs.debian.org/594069 )
which were reported once 0.12.5 entered debian testing. So
it were spotted in 0.12.5, not 0.13. I verfied the bug locally
and indeed, it makes _huge_ difference (0.12.4 vs 0.12.5), --
e.g 600mb mem windows7 hybernation on my machine now takes about
40 minutes to complete instead of ~20 sec in 0.12.4.
I'm reverting whole series (there are 5 patches in total, covering
qcow, qcow2, vmdk and vpc plus infrastructure) for debian 0.12
package. It is sad but there's no other option for now.
/mjt
next prev parent reply other threads:[~2010-08-24 11:06 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 10:40 [Qemu-devel] [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes" Kevin Wolf
2010-08-24 11:02 ` [Qemu-devel] " Stefan Hajnoczi
2010-08-24 11:06 ` Michael Tokarev [this message]
2010-08-24 11:40 ` Kevin Wolf
2010-08-24 11:56 ` Alexander Graf
2010-08-24 12:10 ` Kevin Wolf
2010-08-24 12:12 ` Alexander Graf
2010-08-24 12:18 ` Avi Kivity
2010-08-24 12:21 ` Alexander Graf
2010-08-24 12:27 ` Avi Kivity
2010-08-24 12:35 ` Kevin Wolf
2010-08-24 12:39 ` Avi Kivity
2010-08-24 12:53 ` Kevin Wolf
2010-08-24 12:21 ` Stefan Hajnoczi
2010-08-24 12:23 ` Michael Tokarev
2010-08-24 12:48 ` Juan Quintela
2010-08-24 13:01 ` Anthony Liguori
2010-08-24 13:16 ` Kevin Wolf
2010-08-24 13:29 ` Anthony Liguori
2010-08-24 13:31 ` Avi Kivity
2010-08-24 13:35 ` Anthony Liguori
2010-08-24 13:39 ` Avi Kivity
2010-08-24 13:40 ` Anthony Liguori
2010-08-24 13:44 ` Avi Kivity
2010-08-24 13:56 ` Anthony Liguori
2010-08-25 7:14 ` Avi Kivity
2010-08-25 12:46 ` Anthony Liguori
2010-08-25 13:07 ` Avi Kivity
2010-08-25 13:37 ` Anthony Liguori
2010-08-25 13:23 ` Avi Kivity
2010-08-25 13:42 ` Anthony Liguori
2010-08-25 14:00 ` Avi Kivity
2010-08-25 14:14 ` Anthony Liguori
2010-08-25 14:36 ` Avi Kivity
2010-08-25 15:06 ` Anthony Liguori
2010-08-25 15:15 ` Avi Kivity
2010-08-25 15:21 ` Anthony Liguori
2010-08-25 13:46 ` Anthony Liguori
2010-08-25 14:03 ` Avi Kivity
2010-08-25 14:19 ` Christoph Hellwig
2010-08-25 14:37 ` Avi Kivity
2010-08-25 14:18 ` Christoph Hellwig
2010-08-25 14:26 ` Anthony Liguori
2010-08-25 14:49 ` Daniel P. Berrange
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=4C73A7CB.5000707@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=avi@redhat.com \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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.