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/
Home Products Support Community News


[Xen-devel] [RFC] Credit1: Make weight per-vcpu

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [RFC] Credit1: Make weight per-vcpu
From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Date: Thu, 12 Aug 2010 17:29:55 +0100
Delivery-date: Thu, 12 Aug 2010 09:30:38 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=Nj/Q3vQ/xTJ1KTGRncsCPE1UCiJgT22zb4244SrodNQ=; b=RY9wo1QRqTQgnzI251sJ4RWg540iSocMhsXJ+62nKlnSuln/sWeCWk8ZGRIXP1NNqK s+2+mcmOpUrbuvEvw9cdw9CCHMlOfk4S1gYUlUnn3gMl2kRFU6PzzEQGxEX2DKxFg3n6 YglT6Esz7lr+bogXL4KLGuDGYAxAE4MQKfhBQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=kKTeHp+OrTYh+j2pCNgNfAra0tSrLV5ZXYczn509yZfrsqtKOEnx4ujlypAqXv/wNV Cc03mqOgyPTtQ+ZoEyjb03G7mYR7ZIv3qaD2w0WAtmE5yUOZw+ibZSDr/s+gKWxzplPP YKja1TzyKKSwS2Vkhs/Lo/IszCAp3sUYw/r6Y=
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/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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
At the moment, the "weight" parameter for a VM is set on a per-VM
basis.  This means that when cpu time is scarce, two VMs with the same
weight will be given the same amount of total cpu time, no matter how
many vcpus it has.  I.e., if a VM has 1 vcpu, that vcpu will get x% of
cpu time; if a VM has 2 vcpus, each vcpu will get (x/2)% of the cpu

I believe this is a counter-intuitive interface.  Users often choose
to add vcpus; when they do so, it's with the expectation that a VM
will need and use more cpu time.  In my experience, however, users
rarely change the weight parameter.  So the normal course of events is
for a user to decide a VM needs more processing power, add more cpus,
but doesn't change the weight.  The VM still gets the same amount of
cpu time, but less efficiently allocated (because it's divided).

The attached patch changes the meaning of the "weight" parameter, to
be per-vcpu.  Each vcpu is given the weight.  So if you add an extra
vcpu, your VM will get more cpu time as well.

This patch has been in Citrix XenServer for several releases now
(checked in June 2008), and seems to fit more with customer


Attachment: scheduler.per-vcpu-weight
Description: Binary data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [RFC] Credit1: Make weight per-vcpu, George Dunlap <=