From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famcool@gmail.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [PATCH] VMDK: add monolithic flat image support
Date: Mon, 30 May 2011 14:28:22 +0200 [thread overview]
Message-ID: <4DE38D66.40903@redhat.com> (raw)
In-Reply-To: <BANLkTikZkEXH_UEH0gHnoL88nQOUtmEiWg@mail.gmail.com>
Am 30.05.2011 09:49, schrieb Fam Zheng:
> VMDK multiple file images can not be recognized for now. This patch is
> adding monolithic flat support to it, that is the image type with two
> files, one text descriptor file and a plain data file. This type of
> image can be created in VMWare, with the options "allocate all disk
> space now" and "store virtual disk as a single file" checked.
>
> A VmdkExtent structure is introduced to hold the image "extent"
> information, which makes further adding multi extents support of VMDK
> easy. An image creating option "flat" is added for creating flat
> (preallocated) image.
>
> Signed-off-by: Feiran (Fam) Zheng <famcool@gmail.com>
Ok, seems I commented on so many details that in the end I forgot to add
the general comment. :-)
I think this patch is too big to be well reviewable. You should always
try to make only one logical change in one patch. I think you can split
this at least in two parts: First adding the VmdkExtent data structure
without adding any new functionality, and second adding the monolithic
flat support. Depending on how big the second patch is, you can split it
further into image creation and the rest (or any other split that you
feel is natural).
On two or three hunks I commented that they probably aren't required for
monolithic flat support. They should be separate bugfix or cleanup patches.
Kevin
prev parent reply other threads:[~2011-05-30 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 7:49 [Qemu-devel] [PATCH] VMDK: add monolithic flat image support Fam Zheng
2011-05-30 11:41 ` Kevin Wolf
2011-05-30 12:28 ` Kevin Wolf [this message]
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=4DE38D66.40903@redhat.com \
--to=kwolf@redhat.com \
--cc=famcool@gmail.com \
--cc=hch@lst.de \
--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).