From: Hu Tao <hutao@cn.fujitsu.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>, Peter Lieven <pl@kamp.de>,
Your Name <you@example.com>
Subject: [Qemu-devel] [PATCH v5 0/4] qemu-img: add preallocation=full
Date: Tue, 11 Feb 2014 14:57:22 +0800 [thread overview]
Message-ID: <cover.1392102200.git.you@example.com> (raw)
From: Your Name <you@example.com>
This series implements full image preallocation to create a non-sparse image
file at creation time, both for raw and qcow2 format. The purpose is to avoid
performance deterioration of the guest cause by sparse image.
v5:
- fix wrong calculation of qcow2 metadata size in v4
- remove raw_preallocate2()
- better error out path in raw_create()
- fix coding style
Hu Tao (4):
qapi: introduce PreallocMode and a new PreallocMode full.
raw, qcow2: don't convert file size to sector size
raw-posix: Add full image preallocation option
qcow2: Add full image preallocation option
block/qcow2.c | 91 ++++++++++++++++++++++++++++++++++++++++++++++++-------
block/raw-posix.c | 45 +++++++++++++++++++++------
qapi-schema.json | 12 ++++++++
3 files changed, 128 insertions(+), 20 deletions(-)
--
1.8.0
next reply other threads:[~2014-02-11 6:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 6:57 Hu Tao [this message]
2014-02-11 6:57 ` [Qemu-devel] [PATCH v5 1/4] qapi: introduce PreallocMode and a new PreallocMode full Hu Tao
2014-02-11 6:57 ` [Qemu-devel] [PATCH v5 2/4] raw, qcow2: don't convert file size to sector size Hu Tao
2014-02-11 7:01 ` Hu Tao
2014-02-11 6:57 ` [Qemu-devel] [PATCH v5 3/4] raw-posix: Add full image preallocation option Hu Tao
2014-02-11 6:57 ` [Qemu-devel] [PATCH v5 4/4] qcow2: " Hu Tao
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=cover.1392102200.git.you@example.com \
--to=hutao@cn.fujitsu.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=you@example.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).