2011/3/29 Daniel Veillard <veillard@xxxxxxxxxx>: > On Tue, Mar 29, 2011 at 02:32:19PM +0800, Osier Yang wrote: >> Sample of cputune xml: >> Â <cputune> >> Â Â <shares>2048</shares> >> Â Â <vcpupin vcpu='0' cpuset='0-4,^3'/> >> Â Â <vcpupin vcpu='1' cpuset='1,2'/> >> Â </cputune> >> >> * docs/schemas/domain.rng >> --- >> Âdocs/schemas/domain.rng | Â 32 ++++++++++++++++++++++++++++++++ >> Â1 files changed, 32 insertions(+), 0 deletions(-) >> >> @@ -2198,6 +2219,17 @@ >> Â Â Â Â<param name="minInclusive">1</param> >> Â Â Â</data> >> Â Â</define> >> + Â<define name="vcpuid"> >> + Â Â<data type="unsignedShort"> >> + Â Â Â<param name="pattern">[0-9]+</param> >> + Â Â</data> >> + Â</define> >> + Â<define name="cpushares"> >> + Â Â<data type="unsignedInt"> >> + Â Â Â<param name="pattern">[0-9]+</param> >> + Â Â Â<param name="maxInclusive">262144</param> >> + Â Â</data> >> + Â </define> > > ÂSo there is a bounded value 262144 for cpushares, good but > still no indication of the meaning :-) Actually for ESX I would want this value to be an unrestricted signed integer. ESX has 3 predefined values: low, normal and high. Currently in the scheduler parameters functions I map them to -1, -2, -3. But I'm not sure if that's a thing we should use as a general pattern. I might also calculate the actual values, instead of using special symbolic values. The vSphere docs contain formulas for this conversion. Nevertheless, I vote against this arbitrary (cgroup specific?) upper limit. Matthias -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list