[Libvir] [RFC] Linux-VServer support

[Daniel Veillard]

On Wed, Oct 31, 2007 at 05:14:10PM +0100, Daniel Hokka Zakrisson wrote:
> Daniel Veillard wrote:
> >Are the parameters for the scheduler all integers ? If you really
> >never end up with an information set more structured than that then
> >
> >  <scheduler fill_rate1='100' interval1='1000' fill_rate2='25' 
> >  interval2='1000'
> >             idle_time='1'/>
> >
> >would probably be simpler. The question is would other kind of scheduler
> >use more structured parameters ? Seems to me it's not the case and that
> >ad-hoc parsing to convert {name, value} pairs would just work.
> 
> Actually, the same settings can be applied to the CPUs separately, e.g.
> <scheduler>
>   <param name='fill_rate1'>100</param>
>   <param name='interval1'>1000</param>
>   <cpu id='0'>
>     <param name='idle_time'>1</param>
>     <param name='fill_rate2'>25</param>
>     <param name='interval2'>1000</param>
>   </cpu>
> </scheduler>
> should at some point be possible (it's not in the current patch).

  Hum, I see, first time I see such fine grained scheduling, good to 
know, thanks !
  I still find that

<scheduler fill_rate1='100' interval1='1000'>
  <cpu id='0' idle_time='1' fill_rate2='25' interval2='1000'/>
</scheduler>

would be better than adding the arbitrary <param> element.

Daniel

-- 
Red Hat Virtualization group http://redhat.com/virtualization/
Daniel Veillard      | virtualization library  http://libvirt.org/
veillard at redhat.com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine  http://rpmfind.net/