On Wed, Jan 23, 2013 at 06:44:52PM +0800, Xiao Guangrong wrote: > On 01/23/2013 06:12 PM, Takuya Yoshikawa wrote: > > This patch set mitigates another mmu_lock hold time issue. Although > > this is not enough and I'm thinking of additional work already, this > > alone can reduce the lock hold time to some extent. > > > > It is not worth doing this kind of complex thing, usually, only a few pages on > the invalid list. I think its a good idea - memory freeing can be done outside mmu_lock protection (as long as its bounded). It reduces mmu_lock contention overall. > The *really* heavily case is kvm_mmu_zap_all() which can be speeded > up by using generation number, this is a todo work in kvm wiki: > > http://www.linux-kvm.org/page/TODO: O(1) mmu invalidation using a generation number > > I am doing this work for some weeks and will post the patch out during these days. Can you describe the generation number scheme in more detail, please? -- 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
