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] XEN Proposal

To: "Juergen Gross" <juergen.gross@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] XEN Proposal
From: "George Dunlap" <George.Dunlap@xxxxxxxxxxxxx>
Date: Thu, 11 Dec 2008 19:38:53 +0000
Cc: Chris <hap10@xxxxxxxxxxxxxx>, "Tian, Kevin" <kevin.tian@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Thu, 11 Dec 2008 11:39:16 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=nAf3VKpDeJx5KWKv+JSAoTXV1woEh0B5yRwryHCkFrU=; b=xo/96Ra0Df6xwYHOw0fdzsMQUS3v7IuJKKwiWRuZxyy1zrSqVt8lppTnQ8H3LEEZ5j LgdOyz64wnxqQhuIygcHebthBb2GACJt3Wr7+VbYhW4bMVWyl4JbP1O3CCgxE390D/bF gVzl1zkno2snOIUGCg9z1UcLv8FkD9NXoAVi8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=XjXaVs40j2kB5S+ZJespAXc+48tPWy3Zw73lO6r+Pq8sdIGN1o2eGp0JrDBTJ9z/PH LFZZfBy8IQOivo19cGDX5FeQZyGIs6mBJ9YSmdb3huKtmvHHxYN8o1WThRkL6hUP9p9n 5X/qFbYVjAkZWoJ5+AcraI9mtZ4I5AIhFacoc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <de76405a0812110713t748181d0xe17905b72e57163c@xxxxxxxxxxxxxx>
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>
References: <C56575D3.B12%keir.fraser@xxxxxxxxxxxxx> <573BF77E-A544-448E-BEBB-1DE3503B77CF@xxxxxxxxxxxxxx> <4940B1D2.4060706@xxxxxxxxxxxxxxxxxxx> <de76405a0812110713t748181d0xe17905b72e57163c@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Dec 11, 2008 at 3:13 PM, George Dunlap <dunlapg@xxxxxxxxx> wrote:
> It seems like what you really want is to cap the number of credits the
> VMs can get, and then take them offline when their credits go negative
> (instead of competing for resources in a "best-effort" fashion).  :-)

Actually, it turns out this functionality is already present.

xm sched-credit -d [domid] -c 30

will "cap" the domain to 30% of one cpu, even if there are no other
cpus running.  You should be able to utilize that directly, no
development needed.

 -George

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

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