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] Credit scheduler anamoly

To: "Emmanuel Ackaouy" <ack@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Credit scheduler anamoly
From: "Padala, Pradeep" <pradeep.padala@xxxxxx>
Date: Wed, 22 Nov 2006 12:11:10 -0600
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 22 Nov 2006 10:12:08 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061122095701.GA22481@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccOHJcXCQF/xthcRruIl4RcwePM2gARPBPQ
Thread-topic: [Xen-devel] Credit scheduler anamoly
I will get the latest xen-unstable and try it again. Thanks !

Pradeep 

> -----Original Message-----
> From: Emmanuel Ackaouy [mailto:ack@xxxxxxxxxxxxx] 
> Sent: Wednesday, November 22, 2006 4:57 AM
> To: Padala, Pradeep
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Credit scheduler anamoly
> 
> Are you running a xen-unstable build containing this 
> changeset from November 1st?
> 
> There was a bug in the cap mechanism -- found by your 
> colleagues at HP -- when a physical CPU was contended. This 
> changeset seems to have made things better.
> 
> changeset:   12202:9a4274724794
> user:        Emmanuel Ackaouy <ack@xxxxxxxxxxxxx>
> date:        Wed Nov 01 19:44:34 2006 +0000
> summary:     [XEN] Fix credit scheduler cap mechanism not to 
> over park VCPUs
> 
> 
> On Tue, Nov 21, 2006 at 04:07:00PM -0600, Padala, Pradeep wrote:
> > I sent the following mail without subscribing to the list, and I am 
> > not sure whether the list accepts mails from non-members. I just 
> > subscribed and re-sending the mail. I apologize if you 
> receive multiple copies.
> > 
> > Hi,
> > 
> > I am using the credit scheduler in the xen-unstable trunk and I am 
> > trying to set a cap on the container CPU entitlement. I 
> have two VMs 
> > and two CPUs. The two VMs are restricted to one CPU using 
> the command 
> > xm vcpu-pin. Now, I want to cap the container CPU 
> consumption say to 
> > 4% and 26% of the ONE CPU.
> > 
> > So, I use the following commands.
> > 
> > xm sched-credit -d 73 -c 4
> > xm sched-credit -d 74 -c 26
> > 
> > When I run Xentop, I see this
> > 
> > apache.padalap.1 ------         83    7.0 ...
> > apache.padalap.2 -----r        154   25.5 ...
> > 
> > How is this possible when I cap the first VM to 4% ? Am I 
> missing some 
> > thing ? Does credit scheduler fail to enforce small caps ? 
> Note that I 
> > haven't changed the weights and they are set to default 256 each.
> > 
> > Thanks,
> > Pradeep
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> 

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

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