>Dor Laor wrote: >> The idea to shift/share mmu cache memory between guests is great. >> You do need to take care of proper inter vm locking (kvm_lock lock, >> don't mix the kvm->lock). >> >> > >No, we need to stay away from kvm_lock on anything resembling a hot >path.
If we share the mmu cache globally we need a global lock, its either we'll use kvm_lock or a new one. I think the kvm_lock is sufficient. Anyway the basic intention is not to hold the guest when it needs new mmu cache page. In that case just evacuate another page used by the guest by LRU. There will be a tasklet/timer waking up on certain occasions (maybe after high water mark of evictions) that will re-adjust the mmu cache usage amount the guests. -- Dor. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
