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-users

Re: [Xen-users] xend http interface

To: Jean-David Silberzahn <jds@xxxxxxxxxx>
Subject: Re: [Xen-users] xend http interface
From: Anand <xen.mails@xxxxxxxxx>
Date: Mon, 2 Jan 2006 23:06:37 +0530
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 02 Jan 2006 17:41:42 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=g/NWhpntQV3pr0T9XLhW27JQV6XngTmYr+F0TYF1TMZhfH1e23mdA9XGxfkq2AUqagFZEHpWDGcPO9R6nHu6Ladb3o4YvM/6EnyPfOI4kkXZT641dsLeuh1jBuTb5rJCp3tQpfdx52942YTpgE/9XZIDBizd7H95koJ/qqtStu8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43B94975.5020700@xxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <acb757c00512301017q16cda192g40927118ccbb5924@xxxxxxxxxxxxxx> <43B8FBCD.3030306@xxxxxxxxxx> <acb757c00601020506k58f849f2n102e8ac5b0433a3a@xxxxxxxxxxxxxx> <43B92DE9.8030605@xxxxxxxxxx> <acb757c00601020606ve574749k4642d6244c168dc6@xxxxxxxxxxxxxx> <43B938E4.9050209@xxxxxxxxxx> <acb757c00601020658h46adfb47y1a5110b545c60b5e@xxxxxxxxxxxxxx> <43B94975.5020700@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thanks Jean for all the explanation and information.

On 1/2/06, Jean-David Silberzahn <jds@xxxxxxxxxx> wrote:
Basically xen's SEDF Scheduler enables you to be certain that a given
domain has slice nanoseconds cpu during period nanoseconds. The domain
can use less cpu (if he did not need as much cpu).

Typically a domain on which you ran the command
xm sched-sedf dom-name 5000000 1000000 0 0 0 : has the right to use 1ms
of cpu every 5 ms at most, and if it need it, it is certain to have 1ms
every 5ms
xm sched-sedf dom-name 5000000 1000000 0 1 0 : dom-name can use 1ms
every 5ms at least (if domain needs to be active) and can use more if
others domain don't need the cpu

Playing with this scheduler makes you possible
- Without ExtraTime : to say that a given domain is active at least x
nanoseconds every y nanoseconds
where y is the period you specified
and x is the minimum between the slice you allow to the domain and the
time needed by the domain (not totally certain)

- With ExtraTime : to say that a given domain is active at most x
nanoseconds every y nanoseconds
where x is the minimum between the slice you allow and the time needed
by the domain

What I don't know is how this scheduler acts in smp mode (smp domU) ...


regards,

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