RE: [Xen-devel] another scheduler problem, on x86_64 only?

To:	"Stephan Diestelhorst" <sd386@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	RE: [Xen-devel] another scheduler problem, on x86_64 only?
From:	"Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
Date:	Wed, 13 Jul 2005 10:13:20 -0700
Cc:	Andrew Theurer <habanero@xxxxxxxxxx>
Delivery-date:	Wed, 13 Jul 2005 17:12:09 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcWHzHZJinVGTAqtSpCI53c4JR8+6AAABmmQ
Thread-topic:	[Xen-devel] another scheduler problem, on x86_64 only?

Stephan Diestelhorst wrote:
> Just for clarification:
>    Andrew: Which scheduler did you use? sedf? or bvt?
>    Jun: did you try the bvt scheduler too?
> 
Yes, I tried to both (either by rebuilding xen or sched=<> boot
parameter), confirming like: 
(XEN) Using scheduler: Borrowed Virtual Time (bvt)

I see the problem no matter which scheduler I choose. I think it should
be a schduling issue on x86_64 xenlinux because the cutoff over CPU
utilization is very obvious; 50% max in the top command, and top is not
confused because benchmarks run slower. 

Jun
---
Intel Open Source Technology Center

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

WARNING - OLD ARCHIVES

xen-devel

RE: [Xen-devel] another scheduler problem, on x86_64 only?