Re: [Xen-devel] More on sedf scheduler

[Stephan Diestelhorst <sd386@xxxxxxxxxxxx>]

Thanks,
  what is your dom0 tight loop doing? Heavy I/O?
It looks like dom0 does a lot of I/O, which immediatelly unblocks and then 
gets a higher priority in the L1 extraq, without anybounds on executiontime, 
i.e. slice length. Can you confirm this?

Stephan
> Stephan Diestelhorst wrote:
> >Rob,
> >  That's interesting! Could you provide me with a bit more details?
> >For example your timing parameters for dom0 and domU...
> >Could you just Ctrl-A three times and then show the schedulker runqueues
> > with 'r'?
>
> (XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switch input
> to DOM0).
> (XEN) Scheduler: Simple EDF Scheduler (sedf)
> (XEN) NOW=0x00003659C0E09949
> (XEN) CPU[00] now=59759117961863
> (XEN) RUNQ rq ff18cf80   n: ffbf7e04, p: ffbf7e04
> (XEN)   0: 0.0 has=T p=20000000 sl=15000000 ddl=59759130001778 w=0
> c=1818020375509 sc=-181402283 xtr(yes)=507177757997 ew=0 (27%)
> (XEN)
> (XEN) WAITQ rq ff18cf88   n: ff1bfe04, p: ff1bfe04
> (XEN)   0: 1.0 has=F p=100000000 sl=0 ddl=59759240002401 w=0
> c=2936327068131 sc=131072 xtr(yes)=2936327068131 ew=1 (100%)
> (XEN)
> (XEN) EXTRAQ (penalty) rq ff18cf90   n: ffbf7e0c, p: ffbf7e0c
> (XEN)   0: 0.0 has=T p=20000000 sl=15000000 ddl=59759130001778 w=0
> c=1818020375509 sc=-181402283 xtr(yes)=507177757997 ew=0 (27%)
> (XEN)
> (XEN) EXTRAQ (utilization) rq ff18cf98   n: ffbf7e14, p: ff1bfe14
> (XEN)   0: 0.0 has=T p=20000000 sl=15000000 ddl=59759130001778 w=0
> c=1818020375509 sc=-181402283 xtr(yes)=507177757997 ew=0 (27%)
> (XEN)   1: 1.0 has=F p=100000000 sl=0 ddl=59759240002401 w=0
> c=2936327068131 sc=131072 xtr(yes)=2936327068131 ew=1 (100%)
> (XEN)
> (XEN) not on Q
> [
>
>
> _______________________________________________
> 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