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] Is anyone using the credit scheduler "cap"functionality

To: Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Is anyone using the credit scheduler "cap"functionality?
From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Date: Wed, 21 Jan 2009 10:55:18 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 21 Jan 2009 02:55:44 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=dgUqpMg2IkpsktReAL02zOGHHqIqUDeUjBz7g6hJUtQ=; b=ba3xoat6yHlwkWvH6I8q3d3E6I+KiENThgP/tawUJNkWDkzmaYsj0Zy90r9hIYumuZ n/5rCxg+1gxf9rKvw0O+cMQra4W9Syfyo1yMU5tdl22yH51nBsifVBCpEnQPwSZWaqUE im/7NKOomOc2yMqh7gAvMJ6uAKPEQinGoPKWA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=Shn7yVHCK0irDs/+P2Muy1cMyRme78d0BeBI7/LRzDIghpqPQGtgKEIr7PU9M9fbFB 4uOI4qOAms1Dc5tXfjoRIIkuoVC2emwFZkzu4IsXdWKSVVKsJDJ1MxEuZykTLGUlaFHf 0w+QFH1IMKvORTBxwxtXXXzUGs7ATc5fsdTYk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090121093036.198691808B@xxxxxxxxxxxxxxxxxxxxxx>
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: <de76405a0901201109q522cbbc1ldc9567047fdaba5@xxxxxxxxxxxxxx> <20090121093036.198691808B@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
The general mechanism and interface to the new scheduler will be the
same as the old: weight, credits, &c.  Just a lot of the plumbing will
be re-worked.  It may be a big enough to start a new scheduler,
"credit2", while the kinks get worked out; we'll see.

For those who are using cap to provide QoS: I'm going to be adding a
new feature, a complement to the "cap" feature, which would be a
"floor" or "reservation" feature.  (Haven't thought of a good name for
it yet.)  Just as "cap" will make sure that a given VM never uses more
than X% of a cpu, the "reservation" feature will ensure that a VM can
always get Y% of a cpu if it wants it.  It seems like this may be
closer to what you want -- guarantee a minimum QoS, but allow VMs to
use extra resources if they're available?

At any rate, the cap feature shouldn't be to difficult to keep, so
since people are still using it, I'll do the bit of extra work to keep
it in the new system.  Thanks for the input, all!

Peace,
 -George

On Wed, Jan 21, 2009 at 9:30 AM, Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx> wrote:
> Hi, George
>
> Of course I use "cap".
>
> Would you explain the parameter(s) in your scheduler?
> (keep two or ???)
>
> Thanks
> Atsushi SAKAI
>
>
> George Dunlap <George.Dunlap@xxxxxxxxxxxxx> wrote:
>
>> I'm in the process of revising the credit scheduler design, and I'd
>> like to know how important it is to maintain the "cap" functionality
>> of the credit scheduler.  If you use it, or know of someone who does,
>> could you let me know?
>>
>> If you don't know what it is, you probably aren't using it. :-)
>>
>> Peace,
>>  -George
>>
>> _______________________________________________
>> 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
>

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