[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] atropos again


  • To: Undisclosed.Recipients: ;
  • From: Stephan Diestelhorst <sd386@xxxxxxxxxxxx>
  • Date: Wed, 11 May 2005 11:28:52 +0100
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 11 May 2005 10:28:42 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> > xm sedf DOM PERIOD SLICE LATENCY XTRATIME WEIGHT
> >
> > Where:
> > PERIOD, SLICE: times for guarantees (NANOseconds)
> > LATENCY: currently ignored, recompile with other #define's in
> > sched_sedf.c (ns)
> > XTRATIME: flag, set to 1 and domain gets idle cpu time additional to
> > it's share
> > WEIGHT: use, if you don't want to specify periods/slices, simply
> > distributes the cpu according to these weights
> >
> > Example:
> >
> > xm sedf 1 20000000  5000000 0 0 0
> > xm sedf 2 25000000 12500000 0 0 0
> >
> > -dom 1 gets 25% cpu share (5 ms every 20 ms)
> > -dom 2 gets 50% cpu share (12,5 ms every 25 ms)
> >
> > xm sedf 1 0 0 0 0 0 1
> > xm sedf 2 0 0 0 0 0 5
> >
> > -dom 2 gets 5-times more cpu than dom 1
> > -in total they get 95% - utilisation of fully specified domains
>
> I can understand dom2 get 5 times more cpu than dom1, but why in total
> they get 95%, not 94% or 96%?

This is because I leave 5% unused, just in case :) This is of course 
changeable in sched_sedf.c.

Cheers,
   Stephan

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.