Hi,
Diwaker had provided a program sedf.c on Jan30 to obtain the parameters for
sedf scheduler
(please check
http://lists.xensource.com/archives/html/xen-users/2006-01/msg01228.html).
In my setup, I''d two DomUs and Dom0 was running. I got the following
output
while running the program:
# ./sedf
Domina#0: slice = 15000000, period = 20000000, extratime = 1, latency = 0,
weight = 0
Domina#18: slice = 0, period = 100000000, extratime = 1, latency = 0, weight
= 0
Domina#19: slice = 0, period = 100000000, extratime = 1, latency = 0, weight
= 0
I did not understand few things and would appreciate very much if someone
can clarify the following doubts:
1. Why the period-length is different for Dom0 and DomU''s?
2. Does period-length mean the total time within which *all* domains are
supposed to be scheduled *at least once*?
What does it mean exactly? What does slice-length mean exactly?
3. Can a domU have a slice-length as 0? If so, how can it be scheduled? I
presume that value of extratime flag will make it scheduled, if set. Please
clarify.
4. If extratime flag was not set, do we need to set non-zero slice-length
explicitly to schedule a DomU?
Thanks in advance
,
Amitayu
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi Amitayu,> In my setup, I''d two DomUs and Dom0 was running. I got the following > output while running the program: > > # ./sedf > Domina#0: slice = 15000000, period = 20000000, extratime = 1, latency > = 0, weight = 0 > Domina#18: slice = 0, period = 100000000, extratime = 1, latency = 0, > weight = 0 > Domina#19: slice = 0, period = 100000000, extratime = 1, latency = 0, > weight = 0 > > I did not understand few things and would appreciate very much if > someone can clarify the following doubts: > > 1. Why the period-length is different for Dom0 and DomU''s?Because that''s the default ;-) Domain 0 is running with a guaranteed time slice of 15ms every 20ms and gets also some of the available sparetime, whereas both domu''s are by default set to get only time that is leftover inside the system. Their period (100ms) is (pretty much) meaningless to standard operation.> > 2. Does period-length mean the total time within which *all* domains > are supposed to be scheduled *at least once*? > What does it mean exactly? What does slice-length mean exactly?Hopefully the above explanation clarifies things. Slices are meaningful as a guarantee, that means your domain d will get slice ms cpu-time every period ms. Please note that this guarantee is much stronger than domain d gets say 50% of available CPU time, as this could mean: every year your domain runs for half a year (and then exclusively...). Specifiying periods is exactly as you assume a way of stating the *at-least-once* property you are refering to.> 3. Can a domU have a slice-length as 0? If so, how can it be > scheduled? I presume that value of extratime flag will make it > scheduled, if set. Please clarify.Inded. Please see above. For more detailed comments give me some time, I need to check my own code again ;-)> 4. If extratime flag was not set, do we need to set non-zero > slice-length explicitly to schedule a DomU?Exactly. Otherwise the domain will simply not get any cputime, though existing in the system. Hope that helps, Stephan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
How does one go about building sedf.c. I tried several gcc options but I
keep gettings errors.
Thanks
John
________________________________
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Amitayu Das
Sent: Tuesday, March 28, 2006 2:54 PM
To: xen-users
Subject: [Xen-users] Questions about sedf scheduler
Hi,
Diwaker had provided a program sedf.c on Jan30 to obtain the parameters
for sedf scheduler
(please check
http://lists.xensource.com/archives/html/xen-users/2006-01/msg01228.html
).
In my setup, I''d two DomUs and Dom0 was running. I got the following
output while running the program:
# ./sedf
Domina#0: slice = 15000000, period = 20000000, extratime = 1, latency 0, weight
= 0
Domina#18: slice = 0, period = 100000000, extratime = 1, latency = 0,
weight = 0
Domina#19: slice = 0, period = 100000000, extratime = 1, latency = 0,
weight = 0
I did not understand few things and would appreciate very much if
someone can clarify the following doubts:
1. Why the period-length is different for Dom0 and DomU''s?
2. Does period-length mean the total time within which *all* domains are
supposed to be scheduled *at least once*?
What does it mean exactly? What does slice-length mean exactly?
3. Can a domU have a slice-length as 0? If so, how can it be scheduled?
I presume that value of extratime flag will make it scheduled, if set.
Please clarify.
4. If extratime flag was not set, do we need to set non-zero
slice-length explicitly to schedule a DomU?
Thanks in advance
,
Amitayu
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Thu, 6 Apr 2006 16:01:38 -0400 "John Cianfarani" <jcianfarani@rogers.com> wrote:> How does one go about building sedf.c. I tried several gcc options but I > keep gettings errors.Try: cc -lxenctrl -o sedf_dump sedf_dump.c But I think it is not working correctly now, I get slice/weight = 0 for all domains which is not right. Tim> > > > Thanks > > John > > > > ________________________________ > > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Amitayu Das > Sent: Tuesday, March 28, 2006 2:54 PM > To: xen-users > Subject: [Xen-users] Questions about sedf scheduler > > > > Hi, > > Diwaker had provided a program sedf.c on Jan30 to obtain the parameters > for sedf scheduler > (please check > http://lists.xensource.com/archives/html/xen-users/2006-01/msg01228.html > ). > > In my setup, I''d two DomUs and Dom0 was running. I got the following > output while running the program: > > # ./sedf > Domina#0: slice = 15000000, period = 20000000, extratime = 1, latency > 0, weight = 0 > Domina#18: slice = 0, period = 100000000, extratime = 1, latency = 0, > weight = 0 > Domina#19: slice = 0, period = 100000000, extratime = 1, latency = 0, > weight = 0 > > I did not understand few things and would appreciate very much if > someone can clarify the following doubts: > > 1. Why the period-length is different for Dom0 and DomU''s? > > 2. Does period-length mean the total time within which *all* domains are > supposed to be scheduled *at least once*? > What does it mean exactly? What does slice-length mean exactly? > > 3. Can a domU have a slice-length as 0? If so, how can it be scheduled? > I presume that value of extratime flag will make it scheduled, if set. > Please clarify. > > 4. If extratime flag was not set, do we need to set non-zero > slice-length explicitly to schedule a DomU? > > Thanks in advance > , > Amitayu > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for the help guys, that worked. John -----Original Message----- From: Tim Freeman [mailto:tfreeman@mcs.anl.gov] Sent: Thursday, April 06, 2006 5:24 PM To: John Cianfarani Cc: xen-users@lists.xensource.com; amitayudas@gmail.com Subject: Re: [Xen-users] Questions about sedf scheduler On Thu, 6 Apr 2006 16:01:38 -0400 "John Cianfarani" <jcianfarani@rogers.com> wrote:> How does one go about building sedf.c. I tried several gcc options butI> keep gettings errors.Try: cc -lxenctrl -o sedf_dump sedf_dump.c But I think it is not working correctly now, I get slice/weight = 0 for all domains which is not right. Tim> > > > Thanks > > John > > > > ________________________________ > > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of AmitayuDas> Sent: Tuesday, March 28, 2006 2:54 PM > To: xen-users > Subject: [Xen-users] Questions about sedf scheduler > > > > Hi, > > Diwaker had provided a program sedf.c on Jan30 to obtain theparameters> for sedf scheduler > (please check >http://lists.xensource.com/archives/html/xen-users/2006-01/msg01228.html> ). > > In my setup, I''d two DomUs and Dom0 was running. I got the following > output while running the program: > > # ./sedf > Domina#0: slice = 15000000, period = 20000000, extratime = 1, latency > 0, weight = 0 > Domina#18: slice = 0, period = 100000000, extratime = 1, latency = 0, > weight = 0 > Domina#19: slice = 0, period = 100000000, extratime = 1, latency = 0, > weight = 0 > > I did not understand few things and would appreciate very much if > someone can clarify the following doubts: > > 1. Why the period-length is different for Dom0 and DomU''s? > > 2. Does period-length mean the total time within which *all* domainsare> supposed to be scheduled *at least once*? > What does it mean exactly? What does slice-length mean exactly? > > 3. Can a domU have a slice-length as 0? If so, how can it bescheduled?> I presume that value of extratime flag will make it scheduled, if set. > Please clarify. > > 4. If extratime flag was not set, do we need to set non-zero > slice-length explicitly to schedule a DomU? > > Thanks in advance > , > Amitayu > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Just an FYI... in 3.0.2 running "xm sched-sedf domid" will show the parameters. The method for setting parameters has changed also, xm help sched-sedf. John Cianfarani wrote:> Thanks for the help guys, that worked. > > > John > > -----Original Message----- > From: Tim Freeman [mailto:tfreeman@mcs.anl.gov] > Sent: Thursday, April 06, 2006 5:24 PM > To: John Cianfarani > Cc: xen-users@lists.xensource.com; amitayudas@gmail.com > Subject: Re: [Xen-users] Questions about sedf scheduler > > On Thu, 6 Apr 2006 16:01:38 -0400 > "John Cianfarani" <jcianfarani@rogers.com> wrote: > >> How does one go about building sedf.c. I tried several gcc options but > I >> keep gettings errors. > > Try: > > cc -lxenctrl -o sedf_dump sedf_dump.c > > But I think it is not working correctly now, I get slice/weight = 0 for > all > domains which is not right. > > Tim > > > >> >> >> Thanks >> >> John >> >> >> >> ________________________________ >> >> From: xen-users-bounces@lists.xensource.com >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Amitayu > Das >> Sent: Tuesday, March 28, 2006 2:54 PM >> To: xen-users >> Subject: [Xen-users] Questions about sedf scheduler >> >> >> >> Hi, >> >> Diwaker had provided a program sedf.c on Jan30 to obtain the > parameters >> for sedf scheduler >> (please check >> > http://lists.xensource.com/archives/html/xen-users/2006-01/msg01228.html >> ). >> >> In my setup, I''d two DomUs and Dom0 was running. I got the following >> output while running the program: >> >> # ./sedf >> Domina#0: slice = 15000000, period = 20000000, extratime = 1, latency > >> 0, weight = 0 >> Domina#18: slice = 0, period = 100000000, extratime = 1, latency = 0, >> weight = 0 >> Domina#19: slice = 0, period = 100000000, extratime = 1, latency = 0, >> weight = 0 >> >> I did not understand few things and would appreciate very much if >> someone can clarify the following doubts: >> >> 1. Why the period-length is different for Dom0 and DomU''s? >> >> 2. Does period-length mean the total time within which *all* domains > are >> supposed to be scheduled *at least once*? >> What does it mean exactly? What does slice-length mean exactly? >> >> 3. Can a domU have a slice-length as 0? If so, how can it be > scheduled? >> I presume that value of extratime flag will make it scheduled, if set. >> Please clarify. >> >> 4. If extratime flag was not set, do we need to set non-zero >> slice-length explicitly to schedule a DomU? >> >> Thanks in advance >> , >> Amitayu >> >> > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users