Réf. : Re: [Xen-users] How to get actual DOMU scheduling paramet

Thank you very much, your code seems to work very well. Here are the results for me with the default settings:

# ./sedf
Domina#0: slice = 15000000, period = 20000000, extratime = 1, latency = 0, weight = 0
Domina#2: slice = 0, period = 100000000, extratime = 1, latency = 0, weight = 0
Domina#4: slice = 0, period = 100000000, extratime = 1, latency = 0, weight = 0
Domina#5: slice = 0, period = 100000000, extratime = 1, latency = 0, weight = 0
Domina#6: slice = 0, period = 100000000, extratime = 1, latency = 0, weight = 0

Regards

I'm attaching sedf.c -- it does exactly what you need.

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

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-users] How to get actual DOMU scheduling parameters ?, pierre . gentile Re: [Xen-users] How to get actual DOMU scheduling parameters ?, Diwaker Gupta Réf. : Re: [Xen-users] How to get actual DOMU scheduling parameters ?, pierre . gentile Réf. : Re: [Xen-users] How to get actual DOMU scheduling parameters ?, pierre . gentile <=

Previous by Date:

Re: [Xen-users] Error: Device 769 (vbd) could not be connected. Backend device not found., Stephan Augustin

Next by Date:

[Xen-users] Which linux distribution was it, anders

Previous by Thread:

Réf. : Re: [Xen-users] How to get actual DOMU scheduling parameters ?, pierre . gentile

Next by Thread:

[Xen-users] Error: Device 769 (vbd) could not be connected. Backend device not found., Stephan Augustin

Indexes:

[Date] [Thread] [Top] [All Lists]