qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-block@nongnu.org, Radoslav Gerganov <rgerganov@vmware.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vmdk: Fix next_cluster_sector for compressed write
Date: Thu, 10 Sep 2015 14:02:21 +0200	[thread overview]
Message-ID: <20150910120221.GC4460@noname.redhat.com> (raw)
In-Reply-To: <20150910085803.GB27306@ad.nay.redhat.com>

Am 10.09.2015 um 10:58 hat Fam Zheng geschrieben:
> On Thu, 09/10 11:48, Radoslav Gerganov wrote:
> > On 10.09.2015 11:15, Fam Zheng wrote:
> > > On Thu, 09/10 10:53, Radoslav Gerganov wrote:
> > >> When the VMDK is streamOptimized (or compressed), the
> > >> next_cluster_sector must not be incremented by a fixed number of
> > >> sectors. Instead of this, it must be rounded up to the next consecutive
> > >> sector. Fixing this results in much smaller compressed images.
> > >>
> > >> Signed-off-by: Radoslav Gerganov <rgerganov@vmware.com>
> > > 
> > > Is this patch enough to produce a valid streamOptimized image? Because I
> > > remember there were reports on some other issues with footer or grain markers.
> > > 
> > > Fam
> > 
> > The VMDK spec says that each marker and its associated block must begin on
> > sector boundary which is true before and after my patch.  However, with my
> > patch we don't put empty sectors when we achieve good compression for the
> > current cluster but start the next cluster on the next consecutive sector.
> > 
> > I have also verified that images produced with my patch can be booted in
> > VMware Workstation.
> 
> Thanks, the change looks good to me.
> 
> Reviewed-by: Fam Zheng <famz@redhat.com>

Thanks, applied to the block branch.

Radoslav, for your next patch please remember to always keep qemu-devel
CCed, even if you're sending the patch to a more specific mailing list.
I'm adding it to this mail so that people who aren't subscribed to
qemu-block have a chance to notice the patch.

Kevin

       reply	other threads:[~2015-09-10 12:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1441871594-21252-1-git-send-email-rgerganov@vmware.com>
     [not found] ` <20150910081557.GA27306@ad.nay.redhat.com>
     [not found]   ` <55F143C6.5020401@vmware.com>
     [not found]     ` <20150910085803.GB27306@ad.nay.redhat.com>
2015-09-10 12:02       ` Kevin Wolf [this message]
2015-05-06 12:23 [Qemu-devel] [PATCH] vmdk: Fix next_cluster_sector for compressed write 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=20150910120221.GC4460@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=famz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rgerganov@vmware.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).