From: Avi Kivity <avi@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
stefanha@gmail.com, mjt@tls.msk.ru, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [RFC][STABLE 0.13] Revert "qcow2: Use bdrv_(p)write_sync for metadata writes"
Date: Wed, 25 Aug 2010 17:37:21 +0300 [thread overview]
Message-ID: <4C752AA1.8020203@redhat.com> (raw)
In-Reply-To: <20100825141937.GB31307@lst.de>
On 08/25/2010 05:19 PM, Christoph Hellwig wrote:
> On Wed, Aug 25, 2010 at 08:46:15AM -0500, Anthony Liguori wrote:
>> BTW, something that had the features of qcow2 that people actually used
>> andwas fully asynchronous, performed well, and had a high degree of
>> confidence in data integrity would be a major step forward, not backwards.
> That means you'll actually need to agree on a feature set first.
>
:)
The next image format should be raw-over-btrfs. And we need to continue
developing qcow2, we can't keep moving users from format to format just
because it's complicated.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-08-25 14:53 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
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 [this message]
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=4C752AA1.8020203@redhat.com \
--to=avi@redhat.com \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=mjt@tls.msk.ru \
--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 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).