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

[Xen-devel] Re: Power aware credit scheduler

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Subject: [Xen-devel] Re: Power aware credit scheduler
From: Emmanuel Ackaouy <ackaouy@xxxxxxxxx>
Date: Thu, 19 Jun 2008 16:38:28 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Wei, Gang" <gang.wei@xxxxxxxxx>, "Yu, Ke" <ke.yu@xxxxxxxxx>
Delivery-date: Thu, 19 Jun 2008 07:38:59 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=Lht3NShb2765244FdQvoMpemhjRGg+1v3qukr+Wgd58=; b=MsvYgEo/+37peD4nKASN+i9E6sHewS9Y6gyDIgpNr9sccjsN+VIPsZeBGqCqRAHcVB OEE8zj0OcR1EwDKPJ2ndE5mnhGoTyijFjSO1mZ+VVlpogY+p3O1Cz/XdZCuajxEiv/9t hnLiMRuY+xizq/PyCZ8/vd8kwXPsI8QrgAphU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=PnSVD8IFuYhvovLWgkAwklDECKj2qV5NrFFT2Gwu+L/6aOyOisT5zFGsGooIYZt8Mk ++lVCZ4QXsWKEnU9STyVtIB9agFuvkR5FPoSkzgQralQrNwrYs7m2Od0AGWZ2qmrJDkn 6W0BEBsrd9ML2CFrJnUoPW+w/x2nNE2eNtaW0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <D470B4E54465E3469E2ABBC5AFAC390F024D9454@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <D470B4E54465E3469E2ABBC5AFAC390F024D9444@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <46C27FF3-24A7-48DA-9ABA-BCCB3E9DD30C@xxxxxxxxx> <D470B4E54465E3469E2ABBC5AFAC390F024D9454@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Jun 19, 2008, at 15:32 , Tian, Kevin wrote:
Regardless of any new knobs, a good default behavior might be
to only take a package out of C-state when another non-idle
package has had more than one VCPU active on it over some
reasonable amount of time.

By default, putting multiple VCPUs on the same physical package
when other packages are idle is obviously not always going to
be optimal. Maybe it's not a bad default for VCPUs that are
related (same VM or qemu)? I think Ian P hinted at this. But it
frightens me that you would always do this by default for any set
of VCPUs. Power saving is good but so is memory bandwidth

To enable this feature depends on a control command from system
adminstrator, who knows the tradeoff. From absolute performance
P.O.V, I believe it's not optimal. However if looking from the
performance/watt, i.e. power efficiency angle, power saving due to
package level idle may overwhelm performance impact by keeping
activity in other package. Of course finally memory latency should
be also considered in NUMA system, as you mentioned.

I'm saying something can be done to improve power saving in
the current system without adding a knob. Perhaps you can give
the admin even more power saving abilities with a knob, but it
makes sense to save power when performance is not impacted,
regardless of any knob position.

Also, note I mentioned memory BANDWIDTH and not latency.
It's not the same thing. And I wasn't just thinking about NUMA
systems.

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