On 05/17/2011 09:11 PM, Christoph Hellwig wrote:
On Mon, May 16, 2011 at 04:10:21PM -0500, Anthony Liguori wrote:
To further clarify:
Today cache=none|writethrough|writeback does two things. It:
1) Changes the WCE flag that's visible to the guest
2) Determines whether the host page cache is
Christoph Hellwig wrote:
Why are you even trying this again?
Enabling control of cache setting from qemu monitor will help
users/admins to
accomplish cache value change without depending on the guest.
As explained very clearly last time you
can't change from a writeback-style to a
Anthony Liguori wrote:
On 05/16/2011 03:23 PM, Christoph Hellwig wrote:
Why are you even trying this again? As explained very clearly last
time you
can't change from a writeback-style to a write-through style I/O from
the monitor without creating massive data integrity problems.
To further
On Mon, May 16, 2011 at 04:10:21PM -0500, Anthony Liguori wrote:
To further clarify:
Today cache=none|writethrough|writeback does two things. It:
1) Changes the WCE flag that's visible to the guest
2) Determines whether the host page cache is used for doing guest I/O
As Christoph is very

Currently cache setting of a block device cannot be changed without
restarting a running VM. Following patchset is for enabling dynamic
change of cache setting for block devices through qemu monitor. Code
changes are based on patches from Christoph Hellwig and Prerna Saxena.
Monitor
Why are you even trying this again? As explained very clearly last time you
can't change from a writeback-style to a write-through style I/O from
the monitor without creating massive data integrity problems. See my
patchset that allows changing this from the guest for how it should be
done - I
On 05/16/2011 03:23 PM, Christoph Hellwig wrote:
Why are you even trying this again? As explained very clearly last time you
can't change from a writeback-style to a write-through style I/O from
the monitor without creating massive data integrity problems.
To further clarify:
Today
