From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:42417) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TGVGf-0004B7-Ps for qemu-devel@nongnu.org; Tue, 25 Sep 2012 09:33:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TGVGa-0007Em-23 for qemu-devel@nongnu.org; Tue, 25 Sep 2012 09:33:41 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52735) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TGVGZ-0007Eb-Q9 for qemu-devel@nongnu.org; Tue, 25 Sep 2012 09:33:35 -0400 Message-ID: <5061B2AB.8050509@redhat.com> Date: Tue, 25 Sep 2012 15:33:31 +0200 From: Kevin Wolf MIME-Version: 1.0 References: <506044DE.9060701@gmail.com> <5060524C.2070509@redhat.com> <5060E147.3080306@gmail.com> In-Reply-To: <5060E147.3080306@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] linux aio and cache mode List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: ching Cc: qemu-devel@nongnu.org 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