On 12/19/2011 11:22 AM, Takuya Yoshikawa wrote: >> Yes, it's very conservative. But on the other hand the shrinker is >> tuned for dcache and icache, where there are usually tons of useless >> objects. If we have to free something, I'd rather free them instead of >> mmu pages which tend to get recreated soon. >> > > > OK, to satisfy the requirements, I will do: > > 1. find the guest with the highest (shadow pages / memory) ratio How do you propose to do that efficiently? We may have hundreds of guests, or even more, on one host. Each guest access will involve bouncing a few cache lines. > 2. just zap one page from that guest, keeping the current > conservative rate > > I will update the patch. I think the current rate is too conservative. No idea what a good one is, I don't have a feeling as to the relation between shrinker callbacks and memory pressure. -- error compiling committee.c: too many arguments to function -- 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
