Jack Steiner wrote:
The range invalidates have a performance advantage for the GRU. TLB invalidates
on the GRU are relatively slow (usec) and interfere somewhat with the
performance
of other active GRU instructions. Invalidating a large chunk of addresses with
a single GRU TLBINVAL operation is must faster than issuing a stream of single
page TLBINVALs.
I expect this performance advantage will also apply to other users of mmuops.
In theory this would apply to kvm as well (coalesce tlb flush IPIs,
lookup shadow page table once), but is it really a fast path? What
triggers range operations for your use cases?
--
error compiling committee.c: too many arguments to function
_______________________________________________
general mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general