From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:54752)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lsching17@gmail.com>) id 1TGeSf-0008Eu-Ey
	for qemu-devel@nongnu.org; Tue, 25 Sep 2012 19:22:42 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lsching17@gmail.com>) id 1TGeSe-00082L-DG
	for qemu-devel@nongnu.org; Tue, 25 Sep 2012 19:22:41 -0400
Received: from mail-pb0-f45.google.com ([209.85.160.45]:48280)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lsching17@gmail.com>) id 1TGeSe-00082D-6y
	for qemu-devel@nongnu.org; Tue, 25 Sep 2012 19:22:40 -0400
Received: by pbbrp2 with SMTP id rp2so889191pbb.4
	for <qemu-devel@nongnu.org>; Tue, 25 Sep 2012 16:22:39 -0700 (PDT)
Message-ID: <50623CBC.8050101@gmail.com>
Date: Wed, 26 Sep 2012 07:22:36 +0800
From: ching <lsching17@gmail.com>
MIME-Version: 1.0
References: <506044DE.9060701@gmail.com> <5060524C.2070509@redhat.com>
	<5060E147.3080306@gmail.com> <5061B2AB.8050509@redhat.com>
In-Reply-To: <5061B2AB.8050509@redhat.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] linux aio and cache mode
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org

On 09/25/2012 09:33 PM, Kevin Wolf wrote:
> Am 25.09.2012 00:40, schrieb ching:
>> On 09/24/2012 08:30 PM, Kevin Wolf wrote:
>>> Am 24.09.2012 13:32, schrieb ching:
>>>> Hi all,
>>>>
>>>> My host is qemu-1.1.1 and x64 kernel 3.5.4. The guest is using aio="native"
>>>>
>>>> I am trying to use unsafe cache mode to boost i/o performance.
>>> aio=native requires the image to be opened with O_DIRECT, i.e.
>>> cache=none or cache=directsync. If you specify a different cache option,
>>> it will silently fall back to aio=threads.
>>>
>>> Kevin
>>>
>> will qemu log a entry for the silent fallback?
> No, that's why it's silent. :-)
>
>> Reason:
>>
>> I am testing sparse image on btrfs with mount option: rw,noatime,space_cache,autodefrag,inode_cache
>>
>> i encounter a speed difference (around 2X-3X) between aio=threads,cache=unsafe and aio=native,cache=unsafe
>>
>> aio=threads is much faster, i guest there is conflict between "autodefrag" and linux aio
> This is odd. The point is that with cache=unsafe it shouldn't even be
> using Linux AIO in the first place. I can't see why there would be any
> difference between aio=threads and aio=native with cache=unsafe.
>
> Kevin
>

is it possible to check the open mode of file and whether it is using aio at runtime?