[PVE-User] tc rate limit issue

lyt_yudi lyt_yudi at icloud.com
Tue Mar 24 13:26:10 CET 2015

> 在 2015年3月24日,下午1:44,lyt_yudi <lyt_yudi at icloud.com> 写道:
>> Oh, you should ignore me. I messed up disk IO limits with network limits :-(
>> So you are right, we use TC to limit traffic...
> ok… this is a bug for that (rate limit can’t work)?  


just test it. got some result.

from the GUI, can’t be enabled policy(rate_limit) successfully.

for example:
# tc class show dev tap100i0
“here no content output"

but from the CLI, can enable policy successfully.

# /sbin/tc qdisc add dev tap100i0 handle ffff: ingress
# /sbin/tc filter add dev tap100i0 parent ffff: protocol ip prio 50 estimator 1sec 8sec u32 match ip src police avrate 100kbps drop flowid :1
# /sbin/tc qdisc add dev tap100i0 root handle 1: htb default 1
# /sbin/tc class add dev tap100i0 parent 1: classid 1:1 htb rate 100kbps burst 10kb

# tc class show dev tap100i0
class htb 1:1 root prio 0 rate 800000bit ceil 800000bit burst 10Kb cburst 1600b 

so, when use the OVS to create a network and configure it, there will be a bug, can’t be enabled policy successfully.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-user/attachments/20150324/1f9f9b0b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2345 bytes
Desc: not available
URL: <http://lists.proxmox.com/pipermail/pve-user/attachments/20150324/1f9f9b0b/attachment.bin>

More information about the pve-user mailing list