From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JhNmG-00006F-9P for qemu-devel@nongnu.org; Thu, 03 Apr 2008 07:38:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JhNmE-0008Uj-HZ for qemu-devel@nongnu.org; Thu, 03 Apr 2008 07:38:43 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JhNmE-0008UO-CX for qemu-devel@nongnu.org; Thu, 03 Apr 2008 07:38:42 -0400 Received: from mail2.shareable.org ([80.68.89.115]) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JhNmE-0003Fb-6v for qemu-devel@nongnu.org; Thu, 03 Apr 2008 07:38:42 -0400 Date: Thu, 3 Apr 2008 12:38:34 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH] Asynchronous reliable and configurable cache flush Message-ID: <20080403113833.GB17900@shareable.org> References: <18418.28291.689482.198484@mariner.uk.xensource.com> <200804011846.25975.paul@codesourcery.com> <20080401184501.GA26813@shareable.org> <200804021326.22707.paul@codesourcery.com> <20080402152339.GA15460@shareable.org> <18419.45671.159207.564940@mariner.uk.xensource.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18419.45671.159207.564940@mariner.uk.xensource.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ian Jackson Cc: Marcelo Tosatti , Paul Brook , qemu-devel@nongnu.org Ian Jackson wrote: > > > The cache is dynamically enabled/disabled by the target. This means > > > you've got to close and repopen the file every time it changes, > > > which is likely to get really hairy. > > > > Just open two descriptors :-) > > Doing it with bdrv_aio_flush wasn't too hard, so that's what'll be in > my revised patch shortly. For "uncached" writes, do you wait until _after_ the aio_write has completed before calling aio_fsync, or do you assume the aio_fsync will wait for all aio_writes queued (but not completed) prior to it, as Marcelo Tosatti believes the documentation implies? Thanks, -- Jamie