On 05/30/2012 05:06 PM, Paolo Bonzini wrote:
I think it's beginning to dawn on me that what you have is correct, when
i combine this:
2) target flushes do not have to coincide with a source flush. Writes
after the last source flush _can_ be inconsistent between the source and
the destinatio
On 05/29/2012 02:52 PM, Paolo Bonzini wrote:
Does the drive-mirror coroutine send the writes to the target in the
same order as they are sent to the source? I assume so.
No, it doesn't. It's asynchronous; for continuous replication, the
target knows that it has a consistent view whenever it
Hi,
On 05/24/2012 04:19 PM, Paolo Bonzini wrote:
Here is how the bitmaps are handled when doing I/O on the source:
- after writing to the source:
- clear bit in the volatile in-flight bitmap
- set bit in the persistent dirty bitmap
- after flushing the source:
- msync the persistent b
