From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH] QEMU: fsync AIO writes on flush request Date: Fri, 28 Mar 2008 15:07:03 +0000 Message-ID: <20080328150703.GA19624@shareable.org> References: <20080328150517.GA18077@dmt> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel , Avi Kivity To: qemu-devel@nongnu.org Return-path: Content-Disposition: inline In-Reply-To: <20080328150517.GA18077@dmt> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org Marcelo Tosatti wrote: > Its necessary to guarantee that pending AIO writes have reached stable > storage when the flush request returns. > > Also change fsync() to fdatasync(), since the modification time is not > critical data. > + if (aio_fsync(O_DSYNC, &acb->aiocb) < 0) { > BDRVRawState *s = bs->opaque; > - fsync(s->fd); > + raw_aio_flush(bs); > + fdatasync(s->fd); > + > + /* We rely on the fact that no other AIO will be submitted > + * in parallel, but this should be fixed by per-device > + * AIO queues when allowing multiple CPU's to process IO > + * in QEMU. > + */ > + qemu_aio_flush(); I'm a bit confused by this. Why do you need aio_fsync(O_DSYNC) _and_ synchronous fdatasync() calls? Aren't they equivalent? -- Jamie ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace