External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-03-03 07:33:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

bandwidth: Define schema and create documentation

Browse Source 
Define new 'bandwidth' element with possible child element 'inbound'
and 'outbound' addressing incoming and outgoing traffic respectively:

<bandwidth>
  <inbound average='1000' peak='2000' burst='5120'/>
  <outbound average='500'/>
</bandwidth>

Leaving any element out means not to shape traffic in that
direction.
The units for average and peak (rate) are in kilobytes per second,
for burst (size) are just in kilobytes.
This element can be inserted into domain's 'interface' and
'network'.
This commit is contained in:
Michal Privoznik 2011-07-22 16:07:23 +02:00 committed by Daniel Veillard
parent 239322cbd4
commit a8923162c9
5 changed files with 118 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
docs/formatdomain.html.in
View File

@ -1882,6 +1882,40 @@ qemu-kvm -net nic,model=? /dev/null
<span class="since">Since 0.8.8</span> <span class="since">Since 0.8.8</span>
</p> </p>
<h5><a name="elementQoS">Quality of service</a></h5>
<pre>
...
&lt;devices&gt;
&lt;interface type='network'&gt;
&lt;source network='default'/&gt;
&lt;target dev='vnet0'/&gt;
<b>&lt;bandwidth&gt;
&lt;inbound average='1000' peak='5000' burst='1024'/&gt;
&lt;outbound average='128' peak='256' burst='256'/&gt;
&lt;/bandwidth&gt;</b>
&lt;/interface&gt;
&lt;devices&gt;
...</pre>
<p>
This part of interface XML provides setting quality of service. Incoming
and outgoing traffic can be shaped independently. The
<code>bandwidth</code> element can have at most one <code>inbound</code>
and at most one <code>outbound</code> child elements. Leaving any of these
children element out result in no QoS applied on that traffic direction.
So, when you want to shape only domain's incoming traffic, use
<code>inbound</code> only, and vice versa. Each of these elements have one
mandatory attribute <code>average</code>. It specifies average bit rate on
interface being shaped. Then there are two optional attributes:
<code>peak</code>, which specifies maximum rate at which interface can send
data, and <code>burst</code>, amount of bytes that can be burst at
<code>peak</code> speed. Accepted values for attributes are integer
numbers. The units for <code>average</code> and <code>peak</code> attributes
are kilobytes per second, and for the <code>burst</code> just kilobytes.
<span class="since">Since 0.9.4</span>
</p>
<h4><a name="elementsInput">Input devices</a></h4> <h4><a name="elementsInput">Input devices</a></h4>
<p> <p>

30
docs/formatnetwork.html.in
View File

@ -101,6 +101,36 @@
to this host. <span class="since">Since 0.3.0; 'mode' attribute since to this host. <span class="since">Since 0.3.0; 'mode' attribute since
0.4.2</span></dd> 0.4.2</span></dd>
</dl> </dl>
<h5><a name="elementQoS">Quality of service</a></h5>
<pre>
...
&lt;forward mode='nat' dev='eth0'/&gt;
<b>&lt;bandwidth&gt;
&lt;inbound average='1000' peak='5000' burst='5120'/&gt;
&lt;outbound average='128' peak='256' burst='256'/&gt;
&lt;/bandwidth&gt;</b>
&lt;mac address='00:16:3E:5D:C7:9E'/&gt;
...</pre>
<p>
This part of network XML provides setting quality of service. Incoming
and outgoing traffic can be shaped independently. The
<code>bandwidth</code> element can have at most one <code>inbound</code>
and at most one <code>outbound</code> child elements. Leaving any of these
children element out result in no QoS applied on that traffic direction.
So, when you want to shape only network's incoming traffic, use
<code>inbound</code> only, and vice versa. Each of these elements have one
mandatory attribute <code>average</code>. It specifies average bit rate on
interface being shaped. Then there are two optional attributes:
<code>peak</code>, which specifies maximum rate at which bridge can send
data, and <code>burst</code>, amount of bytes that can be burst at
<code>peak</code> speed. Accepted values for attributes are integer
numbers, The units for <code>average</code> and <code>peak</code> attributes
are kilobytes per second, and for the <code>burst</code> just kilobytes.
The rate is shared equally within domains connected to the network.
<span class="since">Since 0.9.4</span>
</p>
<h3><a name="elementsAddress">Addressing</a></h3> <h3><a name="elementsAddress">Addressing</a></h3>

3
docs/schemas/domain.rng
View File

@ -1189,6 +1189,9 @@
<optional> <optional>
<ref name="deviceBoot"/> <ref name="deviceBoot"/>
</optional> </optional>
<optional>
<ref name="bandwidth"/>
</optional>
</interleave> </interleave>
</define> </define>
<!-- <!--

3
docs/schemas/network.rng
View File

@ -147,6 +147,9 @@
</zeroOrMore> </zeroOrMore>
</element> </element>
</optional> </optional>
<optional>
<ref name="bandwidth"/>
</optional>
<!-- <ip> element --> <!-- <ip> element -->
<zeroOrMore> <zeroOrMore>

48
docs/schemas/networkcommon.rng
View File

@ -47,4 +47,52 @@
</group> </group>
</choice> </choice>
</define> </define>
<define name="bandwidth">
<element name="bandwidth">
<interleave>
<optional>
<element name="inbound">
<ref name="bandwidth-attributes"/>
<empty/>
</element>
</optional>
<optional>
<element name="outbound">
<ref name="bandwidth-attributes"/>
<empty/>
</element>
</optional>
</interleave>
</element>
</define>
<define name="bandwidth-attributes">
<attribute name="average">
<ref name="speed"/>
</attribute>
<optional>
<attribute name="peak">
<ref name="speed"/>
</attribute>
</optional>
<optional>
<attribute name='burst'>
<ref name="BurstSize"/>
</attribute>
</optional>
</define>
<define name="speed">
<data type="unsignedInt">
<param name="pattern">[0-9]+</param>
<param name="minInclusive">1</param>
</data>
</define>
<define name="BurstSize">
<data type="unsignedInt">
<param name="pattern">[0-9]+</param>
<param name="minInclusive">1</param>
</data>
</define>
</grammar> </grammar>