qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Frediano Ziglio <freddy77@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 00/15] qcow/qcow2 cleanups
Date: Mon, 22 Aug 2011 20:14:40 +0200	[thread overview]
Message-ID: <4E529C90.20201@redhat.com> (raw)
In-Reply-To: <1312876010-15361-1-git-send-email-freddy77@gmail.com>

Am 09.08.2011 09:46, schrieb Frediano Ziglio:
> These patches mostly cleanup some AIO code using coroutines.
> Mostly they use stack instead of allocated AIO structure.
> Feel free to collapse it too short.
> 
> Frediano Ziglio (15):
>   qcow: allocate QCowAIOCB structure using stack
>   qcow: QCowAIOCB field cleanup
>   qcow: move some blocks of code to avoid useless variable
>     initialization
>   qcow: embed qcow_aio_read_cb into qcow_co_readv and qcow_aio_write_cb
>     into qcow_co_writev
>   qcow: remove old #undefined code
>   qcow2: removed unused fields
>   qcow2: removed cur_nr_sectors field in QCowAIOCB
>   qcow2: remove l2meta from QCowAIOCB
>   qcow2: remove cluster_offset from QCowAIOCB
>   qcow2: remove common from QCowAIOCB
>   qcow2: reindent and use while before the big jump
>   qcow2: removed QCowAIOCB entirely
>   qcow2: remove memory leak
>   qcow2: small math optimization
>   qcow2: small optimization
> 
>  block/qcow.c           |  378 ++++++++++++++------------------------------
>  block/qcow2-refcount.c |   16 +--
>  block/qcow2.c          |  412 +++++++++++++++++++----------------------------
>  3 files changed, 294 insertions(+), 512 deletions(-)

Can you please rebase this series to current master? I expect that most
conflicts are related to the qemu_malloc -> g_malloc change, so they
should be easy to fix.

One thing I noticed when reading the first two patches is that there is
some state in ACBs that previously was shared across multiple requests
(e.g. the bounce buffer for encryption). It is no longer shared after
you move the ACB to the stack, so each request allocates a new buffer.
Have you checked if this makes a noticeable difference in performance
for encrypted images?

Kevin

  parent reply	other threads:[~2011-08-22 18:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09  7:46 [Qemu-devel] [PATCH v2 00/15] qcow/qcow2 cleanups Frediano Ziglio
2011-08-09  7:46 ` [Qemu-devel] [PATCH v2 01/15] qcow: allocate QCowAIOCB structure using stack Frediano Ziglio
2011-08-09  7:46 ` [Qemu-devel] [PATCH v2 02/15] qcow: QCowAIOCB field cleanup Frediano Ziglio
2011-08-09  7:46 ` [Qemu-devel] [PATCH v2 03/15] qcow: move some blocks of code to avoid useless variable initialization Frediano Ziglio
2011-08-09  7:46 ` [Qemu-devel] [PATCH v2 04/15] qcow: embed qcow_aio_read_cb into qcow_co_readv and qcow_aio_write_cb into qcow_co_writev Frediano Ziglio
2011-08-09  7:46 ` [Qemu-devel] [PATCH v2 05/15] qcow: remove old #undefined code Frediano Ziglio
2011-08-09  7:46 ` [Qemu-devel] [PATCH v2 06/15] qcow2: removed unused fields Frediano Ziglio
2011-08-09  7:46 ` [Qemu-devel] [PATCH v2 07/15] qcow2: removed cur_nr_sectors field in QCowAIOCB Frediano Ziglio
2011-08-09  7:46 ` [Qemu-devel] [PATCH v2 08/15] qcow2: remove l2meta from QCowAIOCB Frediano Ziglio
2011-08-09  7:46 ` [Qemu-devel] [PATCH v2 09/15] qcow2: remove cluster_offset " Frediano Ziglio
2011-08-09  7:46 ` [Qemu-devel] [PATCH v2 10/15] qcow2: remove common " Frediano Ziglio
2011-08-09  7:46 ` [Qemu-devel] [PATCH v2 11/15] qcow2: reindent and use while before the big jump Frediano Ziglio
2011-08-09  7:46 ` [Qemu-devel] [PATCH v2 12/15] qcow2: removed QCowAIOCB entirely Frediano Ziglio
2011-08-09  7:46 ` [Qemu-devel] [PATCH v2 13/15] qcow2: remove memory leak Frediano Ziglio
2011-08-09  7:46 ` [Qemu-devel] [PATCH v2 14/15] qcow2: small math optimization Frediano Ziglio
2011-08-09  7:46 ` [Qemu-devel] [PATCH v2 15/15] qcow2: small optimization Frediano Ziglio
2011-08-22 18:14 ` Kevin Wolf [this message]
2011-08-23 14:00   ` [Qemu-devel] [PATCH v2 00/15] qcow/qcow2 cleanups Frediano Ziglio

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=4E529C90.20201@redhat.com \
    --to=kwolf@redhat.com \
    --cc=freddy77@gmail.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).