| Subject: | Re: [kvm-devel] [Qemu-devel] [PATCH] QEMU: fsync AIO writes on flush request |
|---|---|
| From: | Paul Brook |
| Date: | Fri, 28 Mar 2008 17:00:39 +0000 |
> > Surely you should be using the normal aio notification to wait for the > > aio_fsync to complete before reporting success to the device. > > qemu_aio_flush() will wait for all pending AIO requests (including > aio_fsync) to complete. Then why do you need to separate fdatasync? Paul |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [kvm-devel] [Qemu-devel] [PATCH] QEMU: fsync AIO writes on flush request, Marcelo Tosatti |
|---|---|
| Next by Date: | [Qemu-devel] A bug of running existing windows xp from x86 64 linux host, Jie Zhang |
| Previous by Thread: | Re: [kvm-devel] [Qemu-devel] [PATCH] QEMU: fsync AIO writes on flush request, Marcelo Tosatti |
| Next by Thread: | Re: [kvm-devel] [Qemu-devel] [PATCH] QEMU: fsync AIO writes on flush request, Marcelo Tosatti |
| Indexes: | [Date] [Thread] [Top] [All Lists] |