All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] qcow2: Improve cluster refcount update
Date: Sun, 09 Nov 2008 16:35:34 +0200	[thread overview]
Message-ID: <4916F536.1070009@redhat.com> (raw)
In-Reply-To: <491460D2.4060203@codemonkey.ws>

Anthony Liguori wrote:
> Laurent Vivier wrote:
>> Le vendredi 07 novembre 2008 à 07:59 -0600, Anthony Liguori a écrit :
>>   In all cases #1 is totally useless as it is only cosmetic.
>>
>> #2 improves performance without aligned buffers and with "cache" set to
>> default value.
>>   
>
> I'm currently rewriting the block-raw-posix.c O_DIRECT support.  I'll 
> commit your patches once I finish that.
>
> I'm switching everything to use the aio functions, introducing a 
> memory pool so that we can efficiently allocate memory for new 
> requests without having unbounded memory allocation, and switching all 
> the synchronous functions to use the aio functions.

What about locking?  If clusters are already allocated and we don't need 
COW things are simple (and a global lock should suffice, provided it's 
released before the io is actually submitted), but are you planning to 
parallelize the metadata paths as well?

-- 
error compiling committee.c: too many arguments to function

  parent reply	other threads:[~2008-11-09 14:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06 16:55 [Qemu-devel] [PATCH 0/4] qcow2: Improve cluster refcount update Laurent Vivier
2008-11-06 18:53 ` Anthony Liguori
2008-11-07  8:31   ` Kevin Wolf
2008-11-07  8:44   ` Laurent Vivier
2008-11-07 13:59     ` Anthony Liguori
2008-11-07 15:01       ` Laurent Vivier
2008-11-07 15:37         ` Anthony Liguori
2008-11-07 15:48           ` Laurent Vivier
2008-11-09 14:35           ` Avi Kivity [this message]
2008-11-09 16:32             ` Anthony Liguori
2008-11-10 20:15           ` Andreas Färber
2008-11-10 20:52             ` Anthony Liguori

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=4916F536.1070009@redhat.com \
    --to=avi@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.