From: Stefan Hajnoczi <stefanha@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] vmdk: Fix creating big description file
Date: Tue, 3 Dec 2013 10:13:52 +0100 [thread overview]
Message-ID: <20131203091352.GA13747@stefanha-thinkpad.muc.redhat.com> (raw)
In-Reply-To: <1386038465-8899-1-git-send-email-famz@redhat.com>
On Tue, Dec 03, 2013 at 10:41:05AM +0800, Fam Zheng wrote:
> The buffer for description file was 4096 which only covers a few
> hundred of extents. This changes the buffer to dynamic allocated with
> g_strdup_printf in order to support bigger cases.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
>
> ---
> v2: Use GString for ext_desc_lines.
> Filter cid in reference output.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> block/vmdk.c | 62 +-
> tests/qemu-iotests/059 | 5 +
> tests/qemu-iotests/059.out | 2012 ++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 2055 insertions(+), 24 deletions(-)
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
prev parent reply other threads:[~2013-12-03 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 2:41 [Qemu-devel] [PATCH v2] vmdk: Fix creating big description file Fam Zheng
2013-12-03 9:13 ` Stefan Hajnoczi [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=20131203091352.GA13747@stefanha-thinkpad.muc.redhat.com \
--to=stefanha@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).