From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:59215) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TG6uB-0004KQ-2w for qemu-devel@nongnu.org; Mon, 24 Sep 2012 07:32:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TG6u9-0006yq-TG for qemu-devel@nongnu.org; Mon, 24 Sep 2012 07:32:51 -0400 Received: from mail-pb0-f45.google.com ([209.85.160.45]:47034) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TG6u9-0006yl-Mn for qemu-devel@nongnu.org; Mon, 24 Sep 2012 07:32:49 -0400 Received: by pbbrp2 with SMTP id rp2so1100344pbb.4 for ; Mon, 24 Sep 2012 04:32:48 -0700 (PDT) Message-ID: <506044DE.9060701@gmail.com> Date: Mon, 24 Sep 2012 19:32:46 +0800 From: ching MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] linux aio and cache mode List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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. After googling a while, there are some old web page telling that linux native aio do not use host cache. (http://stackoverflow.com/questions/5664105/buffered-asynchronous-file-i-o-on-linux) is it still valid for recent kernel? do i need to change to aio="threads" to take advantage of unsafe cache mode? Thanks in advance. Regards, ching