From: "Hoggins!" <fuckspam@wheres5.com>
To: lartc@vger.kernel.org
Subject: Re: After kenrel upgrade HTB is not accurate 3.11.6.x
Date: Mon, 06 Jan 2014 22:26:37 +0000 [thread overview]
Message-ID: <52CB2D9D.1040407@wheres5.com> (raw)
In-Reply-To: <800B9523BB5B43D89C2E66781ADCC551@zadziorPC>
Hello,
Seeing that I'm not alone having issues with HTB on newer kernels is
quite relieving. I discovered my problem yesterday, and my only solution
so far was to downgrade the kernel to an acceptable version floor.
Working with kernel 3.10.25 did the trick. I'm sorry, as I cannot help
any further, and my knowledge is really limited on this.
Good luck !
Hoggins!
Le 06/01/2014 22:06, Rados³aw Horodniczy a écrit :
> Hello,
>
> I have (from years on few servers) HTB+IMQ traffic shaping.
>
> Last week i've upgraded my linux server to new release (opensuse 10.3
> to 13.1)
>
> Kernel 2.6.22.12 to Kernel 3.11.6.4
> iptables 1.3.8 to iptables 1.4.19
>
> After upgrade in general everythings works, but shaping is not accurate
>
> Main link is 80Mb/s so limit on HTB script is 80mibit, on old kernel
> it reaches
> over 10240 kbytes and it was fine.
>
> Now on new kernel it reach about 7800kbytes in maximum and cannot go
> higher.
> (workaround for me is set main limit in HTB scripts to 130mibit and it
> can reach output about 10240kbytes)
>
> What I saw first:
>
> tc -s class show dev imq0
> [.....]
> class htb 1:13 parent 1:1 prio 1 rate 200000bit ceil 200000bit burst
> 1492b cburst 1492b
> Sent 5746052 bytes 25213 pkt (dropped 0, overlimits 0 requeues 0)
> rate 0bit 0pps backlog 0b 0p requeues 0
> lended: 25213 borrowed: 0 giants: 0
> tokens: 832500 ctokens: 832500
> [...]
>
> rate shows 0bit,
> so as I found in maillist archive I set
>
> echo 1 > /sys/module/sch_htb/parameters/htb_rate_est
>
> and restart scripts. Now rate shows values, but shapeing is
> still not accurate.
>
> Part of script:
>
> tc qdisc add dev imq0 root handle 1:0 htb default 10
> tc qdisc add dev imq1 root handle 2:0 htb default 10
>
> # Main queue
> tc class add dev imq0 parent 1:0 classid 1:1 htb rate 500mibit ceil
> 500mibit
> tc class add dev imq1 parent 2:0 classid 2:1 htb rate 500mibit ceil
> 500mibit
>
> # Internet link
> tc class add dev imq0 parent 1:1 classid 1:2 htb rate 80mibit ceil
> 80mibit
> tc class add dev imq1 parent 2:1 classid 2:2 htb rate 80mibit ceil
> 80mibit
>
> # default class
> tc class add dev imq0 parent 1:1 classid 1:10 htb rate 10kibit ceil
> 128kibit
> tc qdisc add dev imq0 parent 1:10 handle 10:0 sfq perturb 10
> tc class add dev imq1 parent 2:1 classid 2:10 htb rate 10kibit ceil
> 128kibit
> tc qdisc add dev imq1 parent 2:10 handle 10:0 sfq perturb 10
>
>
> # Per IP rules
>
> tc class add dev imq0 parent 1:2 classid 1:1912 htb rate 10kibit ceil
> 2048kibit prio 2
> tc filter add dev imq0 protocol ip parent 1:0 prio 100 u32 match ip
> dst 10.10.19.12 flowid 1:1912
> tc qdisc add dev imq0 parent 1:1912 handle 1912:0 sfq perturb 10
>
> tc class add dev imq1 parent 2:2 classid 2:1912 htb rate 10kibit ceil
> 1024kibit prio 2
> tc filter add dev imq1 protocol ip parent 2:0 prio 100 u32 match ip
> src 10.10.19.12 flowid 2:1912
> tc qdisc add dev imq1 parent 2:1912 handle 1912:0 sfq perturb 10
>
>
> Pealse help ....
>
> Regards
>
> Radek
>
>
>
> ---
> Ta wiadomo¶æ e-mail jest wolna od wirusów i z³o¶liwego oprogramowania,
> poniewa¿ ochrona avast! Antivirus jest aktywna.
> http://www.avast.com
>
> --
> To unsubscribe from this list: send the line "unsubscribe lartc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2014-01-06 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 21:06 After kenrel upgrade HTB is not accurate 3.11.6.x Radosław Horodniczy
2014-01-06 22:26 ` Hoggins! [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52CB2D9D.1040407@wheres5.com \
--to=fuckspam@wheres5.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.