[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090402171727.GA3127@gondor.apana.org.au>
Date: Fri, 3 Apr 2009 01:17:27 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Avi Kivity <avi@...hat.com>
Cc: Gregory Haskins <ghaskins@...ell.com>,
Rusty Russell <rusty@...tcorp.com.au>, anthony@...emonkey.ws,
andi@...stfloor.org, linux-kernel@...r.kernel.org, agraf@...e.de,
pmullaney@...ell.com, pmorreale@...ell.com, netdev@...r.kernel.org,
kvm@...r.kernel.org, Ingo Molnar <mingo@...e.hu>
Subject: Re: [RFC PATCH 00/17] virtual-bus
On Fri, Apr 03, 2009 at 01:06:10AM +0800, Herbert Xu wrote:
>
> That only happens if the guest immediately does some CPU-intensive
> computation 3ms and assuming its timeslice lasts that long.
>
> In any case, the same thing will happen right now if the host or
> some other guest on the same CPU hogs the CPU for 3ms.
Even better, look at the packet's TOS. If it's marked for low-
latency then vmexit immediately. Otherwise continue.
In the backend you'd just set the marker in shared memory.
Of course invert this for the host => guest direction.
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
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 netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists