Re: [Libvir] [RFC] Linux-VServer support

On Wed, Oct 31, 2007 at 01:36:48PM -0400, Daniel Veillard wrote: > > 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. I don't think so - it makes it harder for an app to process, since they need to know the nams of all the backend specific parameters in order to extract the attribute. By having individual <params> you can easily access them all with XPath - eg /domain/schedular/param/@name can give you a list of all param names very nicely. it also maps to the virSchedInfo data struct nicely