From: Anthony Liguori <anthony@codemonkey.ws>
To: Laurent Vivier <Laurent.Vivier@bull.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch 0/5][v2] qcow2: improve I/O performance with cache=off
Date: Tue, 29 Jul 2008 16:49:44 -0500 [thread overview]
Message-ID: <488F9078.1080001@codemonkey.ws> (raw)
In-Reply-To: <1217367328.3858.14.camel@frecb07144>
Laurent Vivier wrote:
> Le mardi 29 juillet 2008 à 14:15 -0500, Anthony Liguori a écrit :
>
>> Laurent Vivier wrote:
>>
>>> These patches improve qcow2 performance when used with cache=off.
>>>
>>> They modify block-qcow2.c to read/write as many clusters as
>>> possible per bdrv_aio_[read|write]().
>>>
>>>
>> This patch series looks like a pretty good clean up of the code. The
>> perf improvement is a nice side effect too.
>>
>> I'm a little concerned about how much code this touches though. How
>>
>
> Yes, I know, it's why I split it in several patches: easier to review,
> easier to test.
>
>
>> much testing have you done of these changes? Have you tested all of the
>> corner cases (backing files, filling up a disk image, etc.)?
>>
>
> Well, before all I made a lot of review of my modifications, but it must
> also be reviewed by other eyes.
>
> I think it covers a lot of cases, but I didn't test encrypted disk image
> and compressed disk image. The case with backed files was tested only
> with mkfs/fsck/dbench.
>
> If you think these patches are good candidates to be included, I can
> make more tests.
>
Yes, I do think these patches make sense. I would like to see more
testing though. It all seemed pretty clear to me (breaking out the
patches was very helpful!) but I am very worried about corrupting qcow2
images.
Regards,
Anthony Liguori
> Regards,
> Laurent
>
next prev parent reply other threads:[~2008-07-29 21:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 14:13 [Qemu-devel] [patch 0/5][v2] qcow2: improve I/O performance with cache=off Laurent Vivier
2008-07-29 14:13 ` [Qemu-devel] [patch 1/5][v2] Extract code from get_cluster_offset() Laurent Vivier
2008-08-05 14:15 ` Kevin Wolf
2008-08-05 14:28 ` Laurent Vivier
2008-08-05 14:34 ` Kevin Wolf
2008-08-05 14:45 ` Laurent Vivier
2008-07-29 14:13 ` [Qemu-devel] [patch 2/5][v2] Divide get_cluster_offset() Laurent Vivier
2008-08-05 15:13 ` Kevin Wolf
2008-08-05 15:25 ` Laurent Vivier
2008-08-05 15:41 ` Kevin Wolf
2008-07-29 14:13 ` [Qemu-devel] [patch 3/5][v2] Extract compressing part from alloc_cluster_offset() Laurent Vivier
2008-08-06 14:20 ` Kevin Wolf
2008-08-06 14:41 ` Laurent Vivier
2008-08-06 14:56 ` Kevin Wolf
2008-08-06 15:03 ` Laurent Vivier
2008-07-29 14:13 ` [Qemu-devel] [patch 4/5][v2] Aggregate same type clusters Laurent Vivier
2008-08-11 12:10 ` Kevin Wolf
2008-08-11 12:39 ` Laurent Vivier
2008-07-29 14:13 ` [Qemu-devel] [patch 5/5][v2] Try to aggregate free clusters and freed clusters Laurent Vivier
2008-08-11 13:13 ` Kevin Wolf
2008-08-11 14:04 ` Laurent Vivier
2008-08-11 14:42 ` Laurent Vivier
2008-08-11 15:03 ` Kevin Wolf
2008-07-29 19:15 ` [Qemu-devel] [patch 0/5][v2] qcow2: improve I/O performance with cache=off Anthony Liguori
2008-07-29 21:35 ` Laurent Vivier
2008-07-29 21:49 ` Anthony Liguori [this message]
2008-07-29 21:59 ` Laurent Vivier
2008-08-01 14:54 ` Anthony Liguori
2008-08-01 15:05 ` Laurent Vivier
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=488F9078.1080001@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Laurent.Vivier@bull.net \
--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).