[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D30891B.9010104@redhat.com>
Date: Fri, 14 Jan 2011 12:34:19 -0500
From: Rik van Riel <riel@...hat.com>
To: kvm@...r.kernel.org
CC: linux-kernel@...r.kernel.org, Avi Kiviti <avi@...hat.com>,
Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Mike Galbraith <efault@....de>,
Chris Wright <chrisw@...s-sol.org>, ttracy@...hat.com,
dshaks@...hat.com
Subject: Re: [RFC -v5 PATCH 0/4] directed yield for Pause Loop Exiting
On 01/14/2011 03:02 AM, Rik van Riel wrote:
> Benchmark "results":
>
> Two 4-CPU KVM guests are pinned to the same 4 physical CPUs.
I just discovered that I had in fact pinned the 4-CPU KVM
guests to 4 HT threads across 2 cores, and the scheduler
has all kinds of special magic for dealing with HT siblings.
I am now rerunning the tests with the KVM guests bound to
cores 0,2,4,6 to see if that makes a difference.
--
All rights reversed
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists