On Fri, 20 Apr 2012 16:07:41 -0700
Ying Han <ying...@google.com> wrote:
> My understanding of the real pain is the poor implementation of the
> mmu_shrinker. It iterates all the registered mmu_shrink callbacks for
> each kvm and only does little work at a time while holding two big
> locks. I learned from mikew@ (also ++cc-ed) that is causing latency
> spikes and unfairness among kvm instance in some of the experiment
> we've seen.
Last year, I discussed the mmu_shrink issues on kvm ML:
[PATCH 0/4] KVM: Make mmu_shrink() scan nr_to_scan shadow pages
http://www.spinics.net/lists/kvm/msg65231.html
Sadly, we could not find any good way at that time.
Thanks,
Takuya
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
