On Thu, Apr 02, 2009 at 06:57:38PM +0300, Avi Kivity wrote: > > What if the guest sends N packets, then does some expensive computation > (say the guest scheduler switches from the benchmark process to > evolution). So now we have the marker set at packet N, but the host > will not see it until the guest timeslice is up? Well that's fine. The guest will use up the remainder of its timeslice. After all we only have one core/hyperthread here so this is no different than if the packets were held up higher up in the guest kernel and the guest decided to do some computation. Once its timeslice completes the backend can start plugging away at the backlog. Of course it would be better to put the backend on another core that shares the cache or a hyperthread on the same core. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- 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
