[lkml]   [2011]   [Jan]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC -v3 PATCH 0/3] directed yield for Pause Loop Exiting
On 01/04/2011 08:42 AM, Mike Galbraith wrote:
> A couple questions.
> On Mon, 2011-01-03 at 16:26 -0500, Rik van Riel wrote:
> > When running SMP virtual machines, it is possible for one VCPU to be
> > spinning on a spinlock, while the VCPU that holds the spinlock is not
> > currently running, because the host scheduler preempted it to run
> > something else.
> Do you have any numbers?
> If I were to, say, run a 256 CPU VM on my quad, would this help me get
> more hackbench or whatever oomph from my (256X80386/20:) box?

First of all, you can't run 256 guests on x86 kvm. Second, you'll never
see better performance when you overcommit. What this patchset does is
reduce the degradation from utterly ridiculous to something manageable.
This allows a host to deliver reasonable performance when overcommitted
vcpus are actually used, but it's not a good idea to run 64 vcpus on a
32 cpu host.

> > Both Intel and AMD CPUs have a feature that detects when a virtual
> > CPU is spinning on a lock and will trap to the host.
> Does an Intel Q6600 have this trap gizmo (iow will this do anything at
> all for my little box if I were to try it out).

Likely not. Run;a=blob_plain;f=kvm/scripts/vmxcap;hb=HEAD,
look for 'PAUSE-loop exiting'. I think the first processors to include
them were the Nehalem-EXs, and Westmeres have them as well.

error compiling committee.c: too many arguments to function

 \ /
  Last update: 2011-01-04 10:11    [W:0.271 / U:0.020 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site