On 11/15/2011 07:20 AM, Juan Quintela wrote:
Again, I think defaulting DAS to cache=none|directsync is what makes
the most sense here.
I think it is the only sane solution. Otherwise, we need to write the
equivalent of a lock manager, to know _who_ has the storage, and
distributed lock managers are a mess :-(
We can even add a migration blocker for DAS with cache=on. If we can
do dynamic toggling of the cache setting, then that's pretty friendly
at the end of the day.
That could fix the problem also. At the moment that we start migration,
we do an fsync() + switch to O_DIRECT for all filesystems.
As you said, time for implementing fcntl(O_DIRECT).
Yeah, I think this ends up being a very elegant solution.
We always open block devices O_DIRECT to start with. That ensures reads go
directly to disk if its DAS or result in NFS protocol reads.
As long as we fsync on the source (and we do), then we're okay.
For cache=write{back,through}, we would then just fcntl() away O_DIRECT as soon
as we start the guest. Then we can start doing reads through the page cache.
Regards,
Anthony Liguori
Later, Juan.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
