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-users

[Xen-users] Why CPU intensive domain gets 60ms time slice?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Why CPU intensive domain gets 60ms time slice?
From: Thawan Kooburat <kthawan@xxxxxxxxx>
Date: Thu, 3 Mar 2011 19:30:03 -0600
Delivery-date: Thu, 03 Mar 2011 17:31:39 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=MxxXB3yQPO7WKMgnHN+BofiDyULbggm8KaBUQjOUI40=; b=JV1fsJFE7LAZd1fG3JIQBSEeNDUokbg0yFUaMdLuZuWE1a8armcpRpty7Yqq66gY4A o5rxZq+zRfdfFjHiJMNuzyenXsQX8xzu75NSwpTNey8A91EvVLOLHlPJZ5ftzv/ewYjQ XgSXCS8C2hv7S6qIjmP6Ygds3ttPLqe0gjdGE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=MvdmdtbKty9wfz55v5PXoVMNnbY1dBhJqVxew/kT86inwN7DYQX1dRFrvD3+tKexXa cErQ1m9gvC0xHYrztIrOOZUhSpyw1dTqChW+HdSeBDQeT8HEtk+Gp+6w0+JixBKjzmBI ikOMFIvp4mHVxbVvHJ+ZXHQoV+2/gsRlXCi4c=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

My understanding is that the credit scheduler should let each domain
runs at most 30 ms at time.

However, when I set domain cap to 50% and pin it to a single CPU then
run CPU intensive job on that domain, I saw that the domain is running
60 ms at a time. The log show that r_time is 30000000, so credit
scheduler should wake up after 30 ms. However the domain continue to
run until 60 ms.

Is this normal or I miss configure something. I am using Xen
4.0.2-rc1-pre on Fedora 13

Below is the scheduler log from xentrace

CPU2  35923150108817 (+133384208)  switch_infprev    [ old_domid =
0x00007fff, runtime = 53493895 ]
CPU2  35923150109319 (+     502)  switch_infnext    [ new_domid =
0x00000001, time = 1189, r_time = 30000000 ]
CPU2  35923150109874 (+     555)  __enter_scheduler [
prev<domid:edomid> = 0x00007fff : 0x00000002, next<domid:edomid> =
0x00000001 : 0x00000000 ]
CPU2  35923150110264 (+     390)  running_to_runnable [ dom:vcpu = 0x7fff0002 ]
CPU2  35923150111082 (+     818)  runnable_to_running [ dom:vcpu = 0x00010000 ]
CPU2  35923224919179 (+74808097)  unknown (0x0000000000021002)  [
0x00010000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000 ]
CPU2  0 (+       0)  cpu_change        0x00000002
CPU2  35923299725334 (+74806155)  unknown (0x0000000000021002)  [
0x00010000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
0x00000000 ]
CPU2  35923299737972 (+   12638)  switch_infprev    [ old_domid =
0x00000001, runtime = 60007693 ]
CPU2  35923299738504 (+     532)  switch_infnext    [ new_domid =
0x00007fff, time = 60007693, r_time = 4294967295 ]




-- 
Thawan Kooburat

Graduate Student
Department of Computer Science
UW-Madison

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

<Prev in Thread] Current Thread [Next in Thread>