From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB - not borrowing, not exceeding rate
Date: Mon, 09 Jan 2006 23:57:53 +0000 [thread overview]
Message-ID: <43C2F881.3010108@dsl.pipex.com> (raw)
In-Reply-To: <200601081659.24726.kajtek@biezanow.net>
Kajetan Staszkiewicz wrote:
> Here is current setup:
>
> tc qdisc del root dev eth2.24 2>/dev/null
> tc qdisc add root dev eth2.24 handle 1: htb default 1
>
> # main rate limitation for whole connection (802.11a radio link)
> tc class add dev eth2.24 parent 1: classid 1:1 htb rate 15000kbit ceil
> 15000kbit burst 10kbit
Burst too small - it's realated to HZ and also should be at least as big
as child bursts.
http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm#burst
>
> # class for internet connections - this one can use nearly whole link
> tc class add dev eth2.24 parent 1:1 classid 1:6667 htb rate 12000kbit ceil
> 13500kbit burst 100kbit
>
> # class for in-network p2p connections - this one has lower guaranteed rate
> tc class add dev eth2.24 parent 1:1 classid 1:6666 htb rate 3000kbit ceil
> 14000kbit burst 10kbit
> tc qdisc add dev eth2.24 parent 1:6666 handle 6666: sfq perturb 5 quantum
> 1500b
I would condider using htb prio here and sfq peturb causes packet
reordering so 5 is a bit low. SFQ is really best for bulk traffic.
> # now in-network p2p traffic. if it comes from other LANs then direct it to
> # 1:6666
> tc filter add dev eth2.24 protocol ip parent 1:0 u32 match ip src
> 192.168.5.0/24 flowid 1:6666
> tc filter add dev eth2.24 protocol ip parent 1:0 u32 match ip src
> 192.168.4.0/24 flowid 1:6666
I think these should be before the other filters.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-01-09 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-08 15:59 [LARTC] HTB - not borrowing, not exceeding rate Kajetan Staszkiewicz
2006-01-09 23:57 ` Andy Furniss [this message]
2006-01-15 12:49 ` Kajetan Staszkiewicz
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=43C2F881.3010108@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox