From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:51960) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TG8Bj-000213-OX for qemu-devel@nongnu.org; Mon, 24 Sep 2012 08:55:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TG8Bd-0005Te-VL for qemu-devel@nongnu.org; Mon, 24 Sep 2012 08:55:03 -0400 Received: from mx1.redhat.com ([209.132.183.28]:29467) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TG8Bd-0005TR-Mr for qemu-devel@nongnu.org; Mon, 24 Sep 2012 08:54:57 -0400 Message-ID: <5060524C.2070509@redhat.com> Date: Mon, 24 Sep 2012 14:30:04 +0200 From: Kevin Wolf MIME-Version: 1.0 References: <506044DE.9060701@gmail.com> In-Reply-To: <506044DE.9060701@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 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