From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=46764 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Q5hsY-0006E8-FW
	for qemu-devel@nongnu.org; Fri, 01 Apr 2011 13:11:24 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1Q5hsX-0005V3-DO
	for qemu-devel@nongnu.org; Fri, 01 Apr 2011 13:11:22 -0400
Received: from mx1.redhat.com ([209.132.183.28]:31824)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1Q5hsX-0005Ur-53
	for qemu-devel@nongnu.org; Fri, 01 Apr 2011 13:11:21 -0400
Message-ID: <4D95FD80.6050303@redhat.com>
Date: Fri, 01 Apr 2011 18:29:52 +0200
From: Kevin Wolf <kwolf@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] GSoC: Improved image format compatibility
References: <AANLkTimmjMmJBxQv1TTxTb=EU=C_rEgr-YYJSZ1i5zNJ@mail.gmail.com>	<4D92B6A1.30405@mail.berlios.de>	<AANLkTi=gGRGzfxh+QFmtn2n7nRMkwc8K8uvFVfOMv9C7@mail.gmail.com>	<AANLkTinQ9qFy3FoPniVCZYk_C3Bt-JZCnbPBpxuQUUu6@mail.gmail.com>	<4D938074.5090803@mail.berlios.de>
	<AANLkTima7pRswOZLrQKt9G7vKUFDteOSYT6ppMtP2BEw@mail.gmail.com>
In-Reply-To: <AANLkTima7pRswOZLrQKt9G7vKUFDteOSYT6ppMtP2BEw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/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: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Lyu Mitnick <mitnick.lyu@gmail.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@gmail.com>

Am 01.04.2011 17:15, schrieb Lyu Mitnick:
> Hello Stefan
> 
>     Hello Mitnick,
> 
>     asynchronous i/o is also missing in block/vpc.c.
> 
>     All newer block drivers support asynchronous reads and writes,
>     only some old drivers don't.
> 
>     So adding asynchronous i/o to at least some of the old drivers
>     would improve their usability.
> 
>     Look for "aio" in block/*.c to get a starting point.
> 
>     Regards
>     Stefan (W.)
> 
> 
> I look for "aio" in block/*.c as a starting point of asynchronous i/o.
> And I 
> found that there isn't any "aio" keywords in block/vmdk.c. block/vmdk.c
> is used as block driver for the VMDK format. Is it means that asynchronous 
> i/o is also missing in VMDK format?

Yes, the VMDK implementation is completely synchronous.

Kevin