|
xen-devel
Re: [Xen-devel] RE: The caculation of the credit in credit_scheduler
|
To: |
"Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> |
|
Subject: |
Re: [Xen-devel] RE: The caculation of the credit in credit_scheduler |
|
From: |
Juergen Gross <juergen.gross@xxxxxxxxxxxxxx> |
|
Date: |
Wed, 10 Nov 2010 06:46:16 +0100 |
|
Cc: |
George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Dong, Eddie" <eddie.dong@xxxxxxxxx>, "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx> |
|
Delivery-date: |
Tue, 09 Nov 2010 21:47:08 -0800 |
|
Dkim-signature: |
v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=juergen.gross@xxxxxxxxxxxxxx; q=dns/txt; s=s1536b; t=1289367978; x=1320903978; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; z=Message-ID:=20<4CDA31A8.4050308@xxxxxxxxxxxxxx>|Date:=20 Wed,=2010=20Nov=202010=2006:46:16=20+0100|From:=20Juergen =20Gross=20<juergen.gross@xxxxxxxxxxxxxx>|MIME-Version: =201.0|To:=20"Jiang,=20Yunhong"=20<yunhong.jiang@xxxxxxxx m>|CC:=20George=20Dunlap=20<George.Dunlap@xxxxxxxxxxxxx>, =20=0D=0A=20"xen-devel@xxxxxxxxxxxxxxxxxxx"=20<xen-devel@ lists.xensource.com>,=0D=0A=20"Dong,=20Eddie"=20<eddie.do ng@xxxxxxxxx>,=20=0D=0A=20"Zhang,=20Xiantao"=20<xiantao.z hang@xxxxxxxxx>|Subject:=20Re:=20[Xen-devel]=20RE:=20The =20caculation=20of=20the=20credit=20in=20credit_scheduler |References:=20<789F9655DD1B8F43B48D77C5D30659732FD0A5C9@ shsmsx501.ccr.corp.intel.com>=09<4CD95A22.2090902@xxxxxxx ix.com>=20<789F9655DD1B8F43B48D77C5D30659732FD7DF70@shsms x501.ccr.corp.intel.com>|In-Reply-To:=20<789F9655DD1B8F43 B48D77C5D30659732FD7DF70@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |Content-Transfer-Encoding:=207bit; bh=gOiujgssHkUgaRXw7hvwC0RRQlRjmZfHor/9EVbokVQ=; b=O8gwM/S6NOs9+xpBTSzlT0lUU8pCbVwrkWJHFwgwQv972LpOJmjmov+J JxMvXc9OOC1P54p17gk0bcR83YxIwgDfzpbHeLg/PrI+DMoxOfnDXLy1N 6qXjWhIJU6l46Pc//oXNBryC9WxZgnhtPw/xr3ATOo1hLbu1TjgiH2JwN CSBr1CivrHnva0MrPoRsmDDt8p0LLZppPheKX7Db0AiXaEriFnBsd0HiW LbulXRe+oDVd4P5kx9S7d5w/cDrdF; |
|
Domainkey-signature: |
s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Message-ID:Date:From:Organization: User-Agent:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=uignyryxvhgfIIScANEu7lftOBJLiz2OfrP/okeObtQDD+Ok5AHrnjgf jT5SbPjZvecA6MJp34apcMC5c19evxmKD2CTJTN+qJJHmstzWt8LmpFb/ fnjP2w5UaJNlAXOU9sYDPFtxbYKDin2Gxol9XizPSYYSrZN7o0cYqwdr5 Caq+bsDTKdDoZsTd5d4RkPzkyaM1ZB1kNic+gpgiCSeuXV9PDWwzjRSUf y1JgkfeUJQ5YfJ3HHB8tBBQ2VXEIs; |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<789F9655DD1B8F43B48D77C5D30659732FD7DF70@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/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> |
|
Organization: |
Fujitsu Technology Solutions |
|
References: |
<789F9655DD1B8F43B48D77C5D30659732FD0A5C9@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4CD95A22.2090902@xxxxxxxxxxxxx> <789F9655DD1B8F43B48D77C5D30659732FD7DF70@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101030 Iceowl/1.0b1 Icedove/3.0.10 |
On 11/10/10 03:39, Jiang, Yunhong wrote:
-----Original Message-----
From: George Dunlap [mailto:George.Dunlap@xxxxxxxxxxxxx]
Sent: Tuesday, November 09, 2010 10:27 PM
To: Jiang, Yunhong
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Dong, Eddie; Zhang, Xiantao
Subject: Re: The caculation of the credit in credit_scheduler
On 05/11/10 07:06, Jiang, Yunhong wrote:
The reason is how the credit is caculated. Although the 3 HVM domains is pinned
to 2 PCPU and share the 2 CPUs, they will all get 2* 300 credit when credit
account.
That means the I/O intensive HVM domain will never be under credit, thus it will
preempt the CPU intensive whenever it is boost (i.e. after I/O access to QEMU),
and
it is set to be TS_UNDER only at the tick time, and then, boost again.
I suspect that the real reason you're having trouble is that pinning and
the credit mechanism don't work very well together. Instead of pinning,
have you tried using the cpupools interface to make a 2-cpu pool to put
the VMs into? That should allow the credit to be divided appropriately.
I have a quick look in the code, and seems the cpu pool should not help on such
situation. The CPU poll only cares about the CPUs a domain can be scheduled,
but not about the credit caculation.
With cpupools you avoid the pinning. This will result in better credit
calculation results.
Juergen
--
Juergen Gross Principal Developer Operating Systems
TSP ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions e-mail: juergen.gross@xxxxxxxxxxxxxx
Domagkstr. 28 Internet: ts.fujitsu.com
D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
Home