From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [Xen-users] xl doesn't honour the parameter
 cpu_weight from my config file while xm does honour it
Date: Wed, 25 Apr 2012 11:40:20 +0100
Message-ID: <20375.54420.148043.572871@mariner.uk.xensource.com>
References: <20120423193518.GA16134@bloms.de> <1335247525.2397.4.camel@Abyss>
	<20120424121402.GA19331@bloms.de>
	<1335272980.4347.122.camel@zakaz.uk.xensource.com>
	<20120424143329.GB19331@bloms.de>
	<1335279087.4347.186.camel@zakaz.uk.xensource.com>
	<20374.52925.940533.95590@mariner.uk.xensource.com>
	<1335284131.4347.216.camel@zakaz.uk.xensource.com>
	<20374.53940.224705.242658@mariner.uk.xensource.com>
	<20120424182633.GA20286@bloms.de> <20120424193524.GA20565@bloms.de>
	<1335344824.28015.8.camel@zakaz.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <1335344824.28015.8.camel@zakaz.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>, Dario Faggioli <dario.faggioli@citrix.com>, Dieter Bloms <dieter@bloms.de>, xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

Ian Campbell writes ("Re: [Xen-devel] [Xen-users] xl doesn't honour the parameter cpu_weight from my config file while xm does honour it"):
> On Tue, 2012-04-24 at 20:35 +0100, Dieter Bloms wrote:
> > I've made a new patch.
> > Maybe it fit all your needs.
> 
> Thanks, this patch look good to me, I'll leave it to IanJ to decide
> which approach he prefers.

Thanks, I'll take that as an ack.  I've applied Dieter's latest
version, which I like.

I edited the docs message to change "can be set for" to "honoured
by", because variables can be set which will then be ignored.  Eg:

 +=item B<cpu_weight=WEIGHT>
 +
 +A domain with a weight of 512 will get twice as much CPU as a domain
 +with a weight of 256 on a contended host.
 +Legal weights range from 1 to 65535 and the default is 256.
-+Can be set for credit, credit2 and sedf scheduler.
++Honoured by the credit, credit2 and sedf schedulers.

Ian.