From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] qcow2: Allow different cluster sizes
Date: Tue, 19 May 2009 17:59:58 +0200 [thread overview]
Message-ID: <4A12D77E.4030300@redhat.com> (raw)
In-Reply-To: <1242748641-4294-1-git-send-email-kwolf@redhat.com>
Kevin Wolf schrieb:
> Add an option to specify the cluster size of a newly created qcow2 image.
> Default is 4k which is the same value that was hard-coded before.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
This patch obviously depends on the previously sent bdrv_create series.
I just wanted to put it on the list already. It can probably be applied
at the same time as the bdrv_create series.
Kevin
next prev parent reply other threads:[~2009-05-19 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 15:57 [Qemu-devel] [PATCH] qcow2: Allow different cluster sizes Kevin Wolf
2009-05-19 15:59 ` Kevin Wolf [this message]
2009-05-22 13:46 ` [Qemu-devel] " Anthony Liguori
2009-05-20 10:55 ` [Qemu-devel] " Avi Kivity
2009-05-22 13:42 ` [Qemu-devel] " Anthony Liguori
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=4A12D77E.4030300@redhat.com \
--to=kwolf@redhat.com \
--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 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).