From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] qcow2: Improve cluster refcount update
Date: Mon, 10 Nov 2008 14:52:51 -0600 [thread overview]
Message-ID: <49189F23.7080406@codemonkey.ws> (raw)
In-Reply-To: <36DB82BE-B858-4296-B60A-FDA69FF1760F@web.de>
Andreas Färber wrote:
>
> Am 07.11.2008 um 16:37 schrieb Anthony Liguori:
>
>> 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,
>
> I'm not familiar with this area of code, so just as a reminder for
> consideration, recently Blue Swirl added an option to disable AIO.
> Some BSDs as well as Haiku may not have (full) POSIX AIO support.
> Dumping non-AIO code for better performance on Linux would seem to
> counterpoint the broadening platform support?
We can emulate AIO either via a bottom half and synchronous IO (not
great) or using pthreads (better). I have patches for both. Mixing
synchronous IO and asynchronous has all sorts of really ugly consequences.
Regards,
Anthony Liguori
> Andreas
>
>
>
prev parent reply other threads:[~2008-11-10 20:52 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
2008-11-09 16:32 ` Anthony Liguori
2008-11-10 20:15 ` Andreas Färber
2008-11-10 20:52 ` Anthony Liguori [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=49189F23.7080406@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).