On Wed, 2011-03-09 at 16:59 -0800, Shirley Ma wrote: > In theory, for lots of TCP_RR streams, the guest should be able to keep > sending xmit skbs to send vq, so vhost should be able to disable > notification most of the time, then number of guest exits should be > significantly reduced? Why we saw lots of guest exits here still? Is it > worth to try 256 (send queue size) TCP_RRs? If these are single-transaction-at-a-time TCP_RRs rather than "burst mode" then the number may be something other than send queue size to keep it constantly active given the RTTs. In the "bare iron" world at least, that is one of the reasons I added the "burst mode" to the _RR test - because it could take a Very Large Number of concurrent netperfs to take a link to saturation, at which point it might have been just as much a context switching benchmark as anything else :) happy benchmarking, rick jones -- 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
