On Mon, May 11, 2009 at 11:38:09AM -0500, Anthony Liguori wrote: > >Right now it doesn't, but it probably should. > > > > So then with cache=writeback, fsync behaves itself but O_DIRECT writes > do not. Right now O_DIRECT does not do an explicit cache flush, but due to the way barriers are implemented in Linux we do get the cache flush as part of the metadata updates after I/O completion. > fsync is pretty crappy on ext3 default configs. I'm concerned that this > could be considered a DoS by a malicious guest. If it sat in a T_FLUSH > loop, it would potentially bring your system to a crawl, no? It's exactly the same effect as a regular user doing fsync in a loop, whatever that causes on ext3. -- 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
