WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] cpuidle causing Dom0 soft lockups

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] cpuidle causing Dom0 soft lockups
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 21 Jan 2010 10:26:40 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 21 Jan 2010 02:26:59 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B58377E020000780002B3AE@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqagsQFAiJ8AVa4QDas3xtIspcqlAAAXQFd
Thread-topic: [Xen-devel] cpuidle causing Dom0 soft lockups
User-agent: Microsoft-Entourage/12.23.0.091001
On 21/01/2010 10:16, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:

>>> While I don't know this code well, it would seem that we're suffering
>>> from extremely long wakeup times. This suggests that there likely is
>>> a (performance) problem even for smaller numbers of vCPU-s.
>>> Hence, unless it can be fixed before 4.0 releases, I would suggest
>>> disabling C-state management by default again.
>> 
>> It's enabled in 3.4 by feault too though, already. Are there problems there
>> too?
> 
> We never shipped 3.4.x for anything that would normally be run on
> large systems. And 3.4 doesn't support more than 32 vCPU-s per
> domain, hence the problem - even if present - would be hidden.

Hm, okay. Another thing to consider is not using ticket locks when running
on Xen. Regardless of slow wakeup times (and you can't really depend on them
being fast, in general, in a virtualised environment) experiments have shown
that, as you might expect, contended ticket locks perform *abysmally* in
virtualised environments.

Turning off our major source of power-management wins by default in Xen 4.0
is not really a goer.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel