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

[Xen-devel] [PATCH]configuration files(sched-credit)

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH]configuration files(sched-credit)
From: masami.watanabe@xxxxxxxxxxxxxx
Date: Thu, 17 Aug 2006 19:37:03 +0900
Delivery-date: Thu, 17 Aug 2006 03:34:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Currently with the credit scheduler, cpu_weight cannot be assigned to guest 
domains at boot time.(it can be set with xm sched-weight after booting)
This patch allows CPU weight, and CAP to be set by the Xen configuration 
files.


Specification:
The following can be added to the Xen configuration files.

1.CPU WEIGHT [OPTIONAL]
cpu_weight = cpu weight value

-sets the cpu time ratio to be allocated to the domain
-the scale and the default value may vary according to the scheduler used.
 No modification has been made for the bvt scheduler.
--credit scheduler: 1~65535 (default:256)
--bvt scheduler: float value (default:1.0)

2.CAP [OPTIONAL]
cpu_cap= value

-this is only valid when using the credit scheduler
-allots the maximum CPU usage percentage for the domain
-the domain will use
-- (value x 0.01) physical CPUs
  ex: 50 for 0.5 physical CPU
     100 for 1.0 physical CPU
     400 for 4.0 physical CPU
-- default:0.0 (no limit)

Improvements:
- allows cpu_cap to be set in the Xen configuration files
- sets default cpu_cap and cpu_weight values for each scheduler
- passes the cpu_cap and the cpu_weight in the Xen configuration files 
 to xend

Modifications:
-To allow cpu_cap to be set in the Xen configuration files
      python/xen/xm/create.py, python/xen/xend/XendDomainInfo.py,
      python/xen/lowlevel/xc/xc.c
-To allow cpu_cap and cpu_weight in the Xen configuration files to be
 passed to xend
      python/xen/sv/CreateDomain.py, libxc/xenctrl.h, xc_domain.c, 
      python/xen/lowlevel/xc/xc.c
-To set default values for each scheduler
 Previously, the default value, 1.0 had been set for the bvt scheduler by 
the Xen configuration files parsing in XendDomainInfo.py. It has now been 
modified so that default values are set in xc_domain.c after the scheduler 
type has been determined.
In XendDomainInfo.py, the default value is now set to -1
      libxc/xc_domain.c


Signed-off-by: Masami Watanabe <masami.watanabe@xxxxxxxxxxxxxx>

Watanabe

Attachment: configuration_files_sched-credit.patch
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH]configuration files(sched-credit), masami . watanabe <=