From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:33029) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QoFsJ-0006Km-83 for qemu-devel@nongnu.org; Tue, 02 Aug 2011 10:23:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QoFsI-0006xo-6K for qemu-devel@nongnu.org; Tue, 02 Aug 2011 10:23:15 -0400 Received: from mx1.redhat.com ([209.132.183.28]:60113) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QoFsH-0006xb-SR for qemu-devel@nongnu.org; Tue, 02 Aug 2011 10:23:14 -0400 Message-ID: <4E38084C.6010601@redhat.com> Date: Tue, 02 Aug 2011 17:23:08 +0300 From: Avi Kivity MIME-Version: 1.0 References: <1311680948-7648-1-git-send-email-kwolf@redhat.com> In-Reply-To: <1311680948-7648-1-git-send-email-kwolf@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 00/10] block: Coroutine support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin Wolf Cc: stefanha@gmail.com, qemu-devel@nongnu.org On 07/26/2011 02:48 PM, Kevin Wolf wrote: > Depends on Stefan's latest coroutine patches. This series makes qcow and qcow2 > take advantage of the new coroutine infrastructure. Both formats used > synchronous operations for accessing their metadata and blocked the guest CPU > during that time. With coroutines, the I/O will happen asynchronously in the > background and the CPU won't be blocked any more. > Do you plan to convert qcow2 to a fully synchronous design? IMO that will make it more maintainable. Cancellation will need some thought, though. -- error compiling committee.c: too many arguments to function