1
0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-03-07 17:28:15 +00:00

Refactor RNG schema for resource tuning

Split the "resource" define out into multiple smaller
defines, one for each type of resource tuning parameter.
This makes the schema a bit clearer to read

Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
This commit is contained in:
Daniel P. Berrange 2013-04-04 12:40:36 +01:00
parent 8ad126e695
commit 8ef2b2c5b1

View File

@ -498,8 +498,50 @@
</element>
</optional>
<!-- The Blkio cgroup related tunables would go in the blkiotune -->
<optional>
<element name="vcpu">
<optional>
<attribute name="placement">
<choice>
<value>static</value>
<value>auto</value>
</choice>
</attribute>
</optional>
<optional>
<attribute name="cpuset">
<ref name="cpuset"/>
</attribute>
</optional>
<optional>
<attribute name="current">
<ref name="countCPU"/>
</attribute>
</optional>
<ref name="countCPU"/>
</element>
</optional>
<optional>
<ref name="blkiotune"/>
</optional>
<optional>
<ref name="memtune"/>
</optional>
<optional>
<ref name="cputune"/>
</optional>
<optional>
<ref name="numatune"/>
</optional>
</interleave>
</define>
<!-- The Blkio cgroup related tunables would go in the blkiotune -->
<define name="blkiotune">
<element name="blkiotune">
<interleave>
<!-- I/O weight the VM can use -->
@ -522,10 +564,10 @@
</zeroOrMore>
</interleave>
</element>
</optional>
</define>
<!-- All the memory/swap related tunables would go in the memtune -->
<optional>
<define name="memtune">
<element name="memtune">
<!-- Maximum memory the VM can use -->
<optional>
@ -552,34 +594,10 @@
</element>
</optional>
</element>
</optional>
<optional>
<element name="vcpu">
<optional>
<attribute name="placement">
<choice>
<value>static</value>
<value>auto</value>
</choice>
</attribute>
</optional>
<optional>
<attribute name="cpuset">
<ref name="cpuset"/>
</attribute>
</optional>
<optional>
<attribute name="current">
<ref name="countCPU"/>
</attribute>
</optional>
<ref name="countCPU"/>
</element>
</optional>
</define>
<!-- All the cpu related tunables would go in the cputune -->
<optional>
<define name="cputune">
<element name="cputune">
<optional>
<element name="shares">
@ -624,10 +642,10 @@
</element>
</optional>
</element>
</optional>
</define>
<!-- All the NUMA related tunables would go in the numatune -->
<optional>
<define name="numatune">
<element name="numatune">
<optional>
<element name="memory">
@ -660,9 +678,8 @@
</element>
</optional>
</element>
</optional>
</interleave>
</define>
<define name="clock">
<optional>
<element name="clock">