shaba/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-01-11 09:17:52 +03:00
Code Releases Activity

formatdomain.html.in: Document implementation limitation of QoS

Browse Source 
The outbound/@peak is ignored (since QoS was introduced). This is due to
kernel limitation of know allowing ingress filters to have peak just
average rate. However, we should document this limitation to not confuse
users.
This commit is contained in:
Michal Privoznik 2013-07-26 11:42:53 +02:00
parent 0884be37e3
commit d7a4a9b2ff
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/formatdomain.html.in
View File

@ -3530,7 +3530,9 @@ qemu-kvm -net nic,model=? /dev/null
<code>peak</code> speed. Accepted values for attributes are integer <code>peak</code> speed. Accepted values for attributes are integer
numbers. The units for <code>average</code> and <code>peak</code> attributes numbers. The units for <code>average</code> and <code>peak</code> attributes
are kilobytes per second, and for the <code>burst</code> just kilobytes. are kilobytes per second, and for the <code>burst</code> just kilobytes.
<span class="since">Since 0.9.4</span> The <code>inbound</code> can Note the limitation of implementation: the <code>peak</code> attribute in
<code>outbound</code> element is ignored (as linux ingress filters don't
know it yet). <span class="since">Since 0.9.4</span> The <code>inbound</code> can
optionally have <code>floor</code> attribute. This is there for optionally have <code>floor</code> attribute. This is there for
guaranteeing minimal throughput for shaped interfaces. This, however, guaranteeing minimal throughput for shaped interfaces. This, however,
requires that all traffic goes through one point where QoS decisions can requires that all traffic goes through one point where QoS decisions can