[Qemu-devel] Re: Caching modes

2010-09-21 Thread Anthony Liguori
On 09/21/2010 03:57 PM, Christoph Hellwig wrote: On Tue, Sep 21, 2010 at 10:13:01AM -0500, Anthony Liguori wrote: 1) make virtual WC guest controllable. If a guest enables WC,&= ~O_DSYNC. If it disables WC, |= O_DSYNC. Obviously, we can let a user specify the virtual WC mode but it has to

[Qemu-devel] Re: Caching modes

2010-09-21 Thread Christoph Hellwig
On Tue, Sep 21, 2010 at 10:13:01AM -0500, Anthony Liguori wrote: > 1) make virtual WC guest controllable. If a guest enables WC, &= > ~O_DSYNC. If it disables WC, |= O_DSYNC. Obviously, we can let a user > specify the virtual WC mode but it has to be changable during live > migration. I have

[Qemu-devel] Re: Caching modes

2010-09-21 Thread Anthony Liguori
On 09/21/2010 09:26 AM, Christoph Hellwig wrote: On Mon, Sep 20, 2010 at 07:18:14PM -0500, Anthony Liguori wrote: O_DIRECT alone to a pre-allocated file on a normal file system should result in the data being visible without any additional metadata transactions. Anthony, for the third

[Qemu-devel] Re: Caching modes

2010-09-21 Thread Christoph Hellwig
On Mon, Sep 20, 2010 at 07:18:14PM -0500, Anthony Liguori wrote: > O_DIRECT alone to a pre-allocated file on a normal file system should > result in the data being visible without any additional metadata > transactions. Anthony, for the third time: no. O_DIRECT is a non-portable extension in Li

[Qemu-devel] Re: Caching modes

2010-09-21 Thread Kevin Wolf
Am 21.09.2010 02:18, schrieb Anthony Liguori: > On 09/20/2010 06:17 PM, Christoph Hellwig wrote: >> On Mon, Sep 20, 2010 at 03:11:31PM -0500, Anthony Liguori wrote: >> > All read and write requests SHOULD avoid any type of caching in the > host. Any write request MUST complete after th

[Qemu-devel] Re: Caching modes

2010-09-20 Thread Anthony Liguori
On 09/20/2010 06:17 PM, Christoph Hellwig wrote: On Mon, Sep 20, 2010 at 03:11:31PM -0500, Anthony Liguori wrote: All read and write requests SHOULD avoid any type of caching in the host. Any write request MUST complete after the next level of storage reports that the write request has comp

[Qemu-devel] Re: Caching modes

2010-09-20 Thread Christoph Hellwig
On Mon, Sep 20, 2010 at 03:11:31PM -0500, Anthony Liguori wrote: > >>All read and write requests SHOULD avoid any type of caching in the > >>host. Any write request MUST complete after the next level of storage > >>reports that the write request has completed. A flush from the guest > >>MUST comp

[Qemu-devel] Re: Caching modes

2010-09-20 Thread Anthony Liguori
On 09/20/2010 02:34 PM, Christoph Hellwig wrote: On Mon, Sep 20, 2010 at 11:53:02AM -0500, Anthony Liguori wrote: cache=none All read and write requests SHOULD avoid any type of caching in the host. Any write request MUST complete after the next level of storage reports that the write requ

[Qemu-devel] Re: Caching modes

2010-09-20 Thread Christoph Hellwig
On Mon, Sep 20, 2010 at 11:53:02AM -0500, Anthony Liguori wrote: > cache=none > > All read and write requests SHOULD avoid any type of caching in the > host. Any write request MUST complete after the next level of storage > reports that the write request has completed. A flush from the guest