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] Power aware credit scheduler

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Power aware credit scheduler
From: "Ian Pratt" <Ian.Pratt@xxxxxxxxxxxxx>
Date: Thu, 19 Jun 2008 10:14:01 +0100
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, ackaouy@xxxxxxxxx, "Wei, Gang" <gang.wei@xxxxxxxxx>, "Yu, Ke" <ke.yu@xxxxxxxxx>
Delivery-date: Thu, 19 Jun 2008 02:14:40 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <D470B4E54465E3469E2ABBC5AFAC390F024D9444@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcjRyDPly+hYayDgSN6PPLduSJGRXQAIx2dA
Thread-topic: [Xen-devel] Power aware credit scheduler
> c) when cpu's freq is scaled dynamically
>       When cpufreq/Px is enabled, cpu's frequency is adjusted
> to different operation points driven by a on-demand governor. So
> csched_acct may need take frequency difference among cpus into
> consideration and total available credits won't be a simple 300 *
> online cpu_number.

We should also adjust the accounting of the credits consumed in light of
hyperthreading: we should scale the credit we subtract proportional to
the how much of the period was spent competing with another VCPU running
on alternate hyperthread (we can tell this by seeing how much time the
idle thread spent running on the other thread). 

We can then scale the accounting according to some rough notion of the
expected throughput of two hyperthreads e.g. experience on P4 CPU's
suggests that a single VCPU will typically receive something like 65% of
its normal throughput when competing against another thread (total
throughput 130%). We thus scale the amount of credit subtracted between
65% and 100% depending on how much time was spent competing. 

There's an argument that says we should at least have an option to
prevent VCPUs from different guests running against each other in
adjacent threads. This would be introducing a simple kind of gang
scheduling.

Ian  

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