Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M1Rki-0003D5-B4 for qemu-devel@nongnu.org; Tue, 05 May 2009 17:00:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M1Rkd-0003Bv-2i for qemu-devel@nongnu.org; Tue, 05 May 2009 17:00:35 -0400 Received: from [199.232.76.173] (port=57443 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M1Rkc-0003Bs-VB for qemu-devel@nongnu.org; Tue, 05 May 2009 17:00:30 -0400 Received: from verein.lst.de ([213.95.11.210]:38904) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1M1Rkc-0007jr-DE for qemu-devel@nongnu.org; Tue, 05 May 2009 17:00:30 -0400 Date: Tue, 5 May 2009 23:00:28 +0200 From: Christoph Hellwig Subject: Re: [Qemu-devel] [PATCH 0/3] write barrier support Message-ID: <20090505210028.GB24320@lst.de> References: <20090505120804.GA30651@lst.de> <4A0044D5.5010402@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A0044D5.5010402@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Christoph Hellwig , qemu-devel@nongnu.org On Tue, May 05, 2009 at 04:53:25PM +0300, Avi Kivity wrote: > I suggest emulating barriers for format drivers that don't support them > by queuing the writes in the block layer and issuing a flush_all command. We could potentially move the thread pool in posix-aio-compat.c to work ontop of the QEMU block API instead of the Posix API which would take care of this. It might also help replacing the state machines in qcow/qcow2 with a simpler threaded model, but that would need separate investigation.