qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: Fam Zheng <famz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Hu Tao <hutao@cn.fujitsu.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH v2 5/6] qcow2: implement bdrv_preallocate
Date: Wed, 27 Nov 2013 11:03:43 +0100	[thread overview]
Message-ID: <5295C37F.40703@kamp.de> (raw)
In-Reply-To: <529593C5.5060003@redhat.com>

Am 27.11.2013 07:40, schrieb Fam Zheng:
> On 2013年11月27日 14:01, Hu Tao wrote:
>> On Wed, Nov 27, 2013 at 11:01:23AM +0800, Fam Zheng wrote:
>>> On 2013年11月27日 10:15, Hu Tao wrote:
>>>> Signed-off-by: Hu Tao <hutao@cn.fujitsu.com>
>>>> ---
>>>>   block/qcow2.c | 7 +++++++
>>>>   1 file changed, 7 insertions(+)
>>>>
>>>> diff --git a/block/qcow2.c b/block/qcow2.c
>>>> index b054a01..a23fade 100644
>>>> --- a/block/qcow2.c
>>>> +++ b/block/qcow2.c
>>>> @@ -2180,6 +2180,12 @@ static int qcow2_amend_options(BlockDriverState *bs,
>>>>       return 0;
>>>>   }
>>>>
>>>> +static int qcow2_preallocate(BlockDriverState *bs, int64_t offset,
>>>> +                             int64_t length)
>>>> +{
>>>> +    return bdrv_preallocate(bs->file, offset, length);
>>>> +}
>>>> +
>>>
>>> What's the semantics of .bdrv_preallocate? I think you should map
>>> [offset, offset + length) to clusters in image file, and then
>>> forward to bs->file, rather than this direct wrapper.
>>>
>>> E.g. bdrv_preallocate(qcow2_bs, 0, cluster_size) should call
>>> bdrv_preallocate(qcow2_bs->file, offset_off_first_cluster,
>>> cluster_size).
>>
>> You mean data clusters here, right? Is there a single function to get
>> the offset of the first data cluster?
>>
>
> There is a function, qcow2_get_cluster_offset.
This should return no valid offset as long as the cluster is not allocated.

I think you actually have to "write" all clusters of a qcow2 one by one.
Eventually this write could be an fallocate call instead of a zero write.

Peter

  reply	other threads:[~2013-11-27 10:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27  2:15 [Qemu-devel] [RFC PATCH v2 0/6] qemu-img: add preallocation=full Hu Tao
2013-11-27  2:15 ` [Qemu-devel] [RFC PATCH v2 1/6] block: introduce prealloc_mode Hu Tao
2013-11-27  2:15 ` [Qemu-devel] [RFC PATCH v2 2/6] block: add BlockDriver.bdrv_preallocate Hu Tao
2013-11-27  2:35   ` Fam Zheng
2013-11-27  2:15 ` [Qemu-devel] [RFC PATCH v2 3/6] block/raw-posix: implement bdrv_preallocate Hu Tao
2013-11-27  2:40   ` Fam Zheng
2013-11-27  2:15 ` [Qemu-devel] [RFC PATCH v2 4/6] raw-posix: Add full image preallocation option Hu Tao
2013-11-27  2:15 ` [Qemu-devel] [RFC PATCH v2 5/6] qcow2: implement bdrv_preallocate Hu Tao
2013-11-27  3:01   ` Fam Zheng
2013-11-27  6:01     ` Hu Tao
2013-11-27  6:40       ` Fam Zheng
2013-11-27 10:03         ` Peter Lieven [this message]
2013-11-27 10:07           ` Fam Zheng
2013-11-27 10:13             ` Peter Lieven
2013-11-28  8:48               ` Hu Tao
2013-11-28 10:03                 ` Peter Lieven
2013-12-11  7:33                   ` Hu Tao
2013-12-16  8:24                     ` Hu Tao
2013-12-16  9:21                     ` Fam Zheng
2013-12-17  2:03                       ` Hu Tao
2013-11-27  2:15 ` [Qemu-devel] [RFC PATCH v2 6/6] qcow2: Add full image preallocation option Hu Tao
2013-11-27  3:22 ` [Qemu-devel] [RFC PATCH v2 0/6] qemu-img: add preallocation=full Fam Zheng

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=5295C37F.40703@kamp.de \
    --to=pl@kamp.de \
    --cc=famz@redhat.com \
    --cc=hutao@cn.fujitsu.com \
    --cc=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).