From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB - prio and rate
Date: Sun, 04 Dec 2005 16:05:07 +0000 [thread overview]
Message-ID: <1133712309.15937.19.camel@pc.local> (raw)
In-Reply-To: <BF782D07436CAE4B931BFA5B2C68FF4F0F8E44@bmts1.ad.bmtseatech.co.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1774 bytes --]
On Sun, 2005-12-04 at 10:14 -0500, Jeffrey B. Ferland wrote:
> To prioritize, you must classify. HTB allows prioritization and
> classification... and limitation as well.
Seems the combination of TBF and PRIO does too.
> Attaching something like this: Root --> TBF --> Prio would be nice,
> but I haven't succeeded in ever attaching anything to a TBF.. or any
> other "classless" qdisc.
Hrm. I *think* that is what I have done with the help of
http://edseek.com/~jasonb/articles/traffic_shaping/scenarios.html#guarprio
qdisc tbf 1: rate 120000bit burst 1199b lat 4294.9s
Sent 26658509 bytes 511623 pkt (dropped 176, overlimits 8118 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
qdisc prio 2: parent 1:1 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 26658509 bytes 511623 pkt (dropped 0, overlimits 0 requeues 8118)
rate 0bit 0pps backlog 0b 0p requeues 8118
qdisc sfq 10: parent 2:1 limit 128p quantum 1452b perturb 20sec
Sent 3525247 bytes 56520 pkt (dropped 0, overlimits 0 requeues 88)
rate 0bit 0pps backlog 0b 0p requeues 88
qdisc sfq 20: parent 2:2 limit 128p quantum 1452b perturb 20sec
Sent 1939846 bytes 19450 pkt (dropped 0, overlimits 0 requeues 5457)
rate 0bit 0pps backlog 0b 0p requeues 5457
qdisc sfq 30: parent 2:3 limit 128p quantum 1452b perturb 20sec
Sent 21193416 bytes 435653 pkt (dropped 0, overlimits 0 requeues 2573)
rate 0bit 0pps backlog 0b 0p requeues 2573
I'm using iptables/pp2p to classify bittorrent into 2:3 and it seems to
be working just fine (even classifying the outgoing ACKs from the
bittorrent download there) while I have classified "ping" into 2:1 and
it seems to be working there.
b.
--
My other computer is your Microsoft Windows server.
Brian J. Murrell
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-12-04 16:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 13:57 [LARTC] HTB - prio and rate Mark Lidstone
2005-12-02 20:25 ` Andreas Klauer
2005-12-02 20:31 ` Brian J. Murrell
2005-12-02 20:48 ` Andreas Klauer
2005-12-02 22:24 ` Brian J. Murrell
2005-12-03 6:04 ` Andreas Klauer
2005-12-03 23:14 ` Brian J. Murrell
2005-12-04 2:32 ` Jeffrey B. Ferland
2005-12-04 3:17 ` Jason Boxman
2005-12-04 3:26 ` Jason Boxman
2005-12-04 6:24 ` Andreas Klauer
2005-12-04 13:48 ` Brian J. Murrell
2005-12-04 15:14 ` Jeffrey B. Ferland
2005-12-04 16:05 ` Brian J. Murrell [this message]
2005-12-05 9:40 ` Mark Lidstone
2005-12-05 18:15 ` Andreas Klauer
2005-12-06 12:27 ` Mark Lidstone
2005-12-13 8:51 ` Mark Lidstone
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=1133712309.15937.19.camel@pc.local \
--to=brian@interlinx.bc.ca \
--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.