On Thu, Jun 16, 2011 at 1:44 AM, Anthony Liguori <[email protected]> wrote:
>> That's probably why it's fast, it doesn't preserve data integrity :(
>
> Actually, I misread the code. It does unstable writes but it does do
> fsync() on FLUSH.
Yes. That's fine, right? Or did we misread how virtio block devices
are supposed to work?
Btw, unstable writes doesn't really explain why *read* performance is better.
Pekka
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
