On Fri, 05 Dec 2008 Cam Macdonell wrote : > That is interesting. Linux has a new feature in 2.6.27 called kernel > shared memory that merges identical pages and marks them COW. If a > write occurs, then those pages are no longer shared and the writing VM > gets their own copy.
At high level, this is what we do as well. We may have different ways to detect identical pages. But I am not an expert on this. > If you can tell me, how does VMware handle it? If VM1 changes one of > these shared pages then does that VM get its own copy of it? What I > want is if one VM writes to a page, I want the other VM to see the > changes. If your product can do that, then I would be interested. No, VM1 write to the page, VM1 gets its own copy. Other VMs don't see the update. Again, IMHO, if an update is visible to other VMs, the isolation property of a VM is no more. If you want to a writeable cache for files, you start to deal with consistency issues between writes. Things seem to get complicated quickly. Why do you need other VMs to see an update? Can you use socket/datagram for that if the updates are rare? ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ open-vm-tools-devel mailing list open-vm-tools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
