From: Fam Zheng <famz@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: John Snow <jsnow@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Qemu-block <qemu-block@nongnu.org>, Kevin Wolf <kwolf@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Manos Pitsidianakis <el13635@mail.ntua.gr>
Subject: Re: [Qemu-devel] Persistent bitmaps for non-qcow2 formats
Date: Mon, 28 Aug 2017 10:57:06 +0800 [thread overview]
Message-ID: <20170828025706.GA18194@lemon.lan> (raw)
In-Reply-To: <b0d72a26-2052-ecc6-67f5-d32572804ebf@redhat.com>
On Fri, 08/25 15:44, Max Reitz wrote:
> Well, OK. The main argument against supporting anything but qcow2 is
> "if you want features, use qcow2; and we are working on making qcow2 as
> fast as possible." I think that's a very good argument still. At some
> point I (and probably others, too) had the idea of making qcow2 files in
> raw layout:
Yes! I think this idea makes a whole lot of sense, too. Metadata tables can be
generated so old implementation can still use it.
Fam
> Have the data as a blob, just like a raw file, padded by
> metadata around it. An autoclear flag would specify that the qcow2 file
> is in this format, and if so, you could simply access it like a raw file
> and should have exactly the same speed as a raw file. Maybe that would
> solve this whole issue, too?
next prev parent reply other threads:[~2017-08-28 2:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 19:07 [Qemu-devel] Persistent bitmaps for non-qcow2 formats John Snow
2017-08-23 8:59 ` Vladimir Sementsov-Ogievskiy
2017-08-23 18:04 ` Vladimir Sementsov-Ogievskiy
2017-08-23 18:37 ` Vladimir Sementsov-Ogievskiy
2017-08-25 0:55 ` John Snow
2017-08-25 12:05 ` Vladimir Sementsov-Ogievskiy
2017-08-25 13:44 ` Max Reitz
2017-08-28 2:57 ` Fam Zheng [this message]
2017-08-28 18:11 ` John Snow
2017-08-29 9:26 ` Yaniv Lavi (Dary)
2017-08-30 10:35 ` Max Reitz
2017-08-30 12:58 ` Yaniv Lavi (Dary)
2017-08-30 21:25 ` John Snow
2017-08-31 7:53 ` Yaniv Lavi (Dary)
2017-09-05 13:01 ` Kevin Wolf
2017-09-05 13:18 ` Fam Zheng
2017-09-05 13:27 ` Kevin Wolf
2017-09-05 13:39 ` Fam Zheng
2017-09-05 14:39 ` Kevin Wolf
2017-08-29 1:18 ` John Snow
2017-08-29 14:30 ` Eric Blake
2017-08-29 21:02 ` John Snow
2017-08-30 11:18 ` Max Reitz
2017-08-30 11:14 ` Max Reitz
2017-08-23 17:31 ` Max Reitz
2017-08-23 17:44 ` John Snow
2017-09-05 13:15 ` Kevin Wolf
2017-08-30 13:36 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-08-30 13:45 ` Daniel P. Berrange
2017-08-30 21:39 ` John Snow
2017-09-05 11:46 ` [Qemu-devel] " Kevin Wolf
2017-09-06 13:11 ` 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=20170828025706.GA18194@lemon.lan \
--to=famz@redhat.com \
--cc=el13635@mail.ntua.gr \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.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.