From: "Gavin" <gavin@raha.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb ceiling
Date: Fri, 05 Apr 2002 11:58:58 +0000 [thread overview]
Message-ID: <marc-lartc-101800796732146@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101799477322990@msgid-missing>
I tried it with a minimal config - two classes, each with rate: 256Kbit and
ceiling: 512Kbit and one dest. IP address in each, as well as a default
class. Each specified machine could only pull 256Kbit maximum, either alone
or with the other downloading as well.
Output of tc -s qdisc show dev eth1:
qdisc sfq 50: quantum 1514b perturb 10sec
Sent 7506464 bytes 4984 pkts (dropped 0, overlimits 0)
backlog 6p
qdisc sfq 40: quantum 1514b perturb 10sec
Sent 4275617 bytes 2829 pkts (dropped 0, overlimits 0)
backlog 3p
qdisc sfq 10: quantum 1514b perturb 10sec
Sent 287102 bytes 542 pkts (dropped 0, overlimits 0)
qdisc htb 1: r2q 100 default 10 dcache 0
deq_util 1/1000000 deq_rate 125 trials_per_deq 0
dcache_hits 0 direct_packets 0
Sent 12069183 bytes 8355 pkts (dropped 0, overlimits 15537)
backlog 9p
Output of tc -s class show dev eth1:
class htb 1:10 root leaf 10: prio 0 rate 2Mbit ceil 2Mbit burst 15Kb cburst
4220b
Sent 331368 bytes 678 pkts (dropped 0, overlimits 32)
rate 107bps
lended: 678 borrowed: 0 giants: 0 injects: 0
tokens: 47825 ctokens: 13015
class htb 1:2 root prio 0 rate 5Mbit ceil 5Mbit burst 15Kb cburst 8151b
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
lended: 0 borrowed: 0 giants: 0 injects: 0
tokens: 19199 ctokens: 10190
class htb 1:40 root leaf 40: prio 0 rate 256Kbit ceil 512Kbit burst 15Kb
cburst 2254b
Sent 4275671 bytes 2830 pkts (dropped 0, overlimits 0)
rate 226bps
lended: 2830 borrowed: 0 giants: 0 injects: 0
tokens: 382801 ctokens: 27588
class htb 1:50 root leaf 50: prio 0 rate 256Kbit ceil 512Kbit burst 15Kb
cburst 2254b
Sent 8214460 bytes 5467 pkts (dropped 0, overlimits 0)
rate 546bps
lended: 5467 borrowed: 0 giants: 0 injects: 0
tokens: 382801 ctokens: 27588
Output of htb.init compile:
tc qdisc del dev eth1 root
tc qdisc add dev eth1 root handle 1 htb default 10 r2q 100
tc class add dev eth1 parent 1:2 classid 1:10 htb rate 2Mbit ceil 2Mbit
burst 15k
tc qdisc add dev eth1 parent 1:10 handle 10 sfq perturb 10
tc class add dev eth1 parent 1:2 classid 1:40 htb rate 256Kbit ceil 512Kbit
burst 15k
tc qdisc add dev eth1 parent 1:40 handle 40 sfq perturb 10
tc filter add dev eth1 parent 1:0 protocol ip prio 100 u32 match ip dst
10.0.0.20 classid 1:40
tc class add dev eth1 parent 1:2 classid 1:50 htb rate 256Kbit ceil 512Kbit
burst 15k
tc qdisc add dev eth1 parent 1:50 handle 50 sfq perturb 10
tc filter add dev eth1 parent 1:0 protocol ip prio 100 u32 match ip dst
10.0.0.150 classid 1:50
tc class add dev eth1 parent 1: classid 1:2 htb rate 5Mbit burst 15k
Gavin
----- Original Message -----
From: "Martin Devera" <devik@cdi.cz>
To: "Stef Coene" <stef.coene@docum.org>
Cc: "Gavin" <gavin@raha.com>; <LARTC@mailman.ds9a.nl>
Sent: Friday, April 05, 2002 1:40 PM
Subject: Re: [LARTC] htb ceiling
> > > tc qdisc add dev eth1 root handle 1 htb default 10 r2q 100
> > > tc class add dev eth1 parent 1: classid 1:2 htb rate 5Mbit burst 15k
> > > tc class add dev eth1 parent 1:2 classid 1:40 htb rate 256Kbit ceil
512Kbit
> > > burst 15k
> > > tc qdisc add dev eth1 parent 1:40 handle 40 sfq perturb 10
> > > tc filter add dev eth1 parent 1:0 protocol ip prio 100 u32 match ip
dst
> > > 10.0.0.2 classid 1:40
> > >
> > > - this allows 10.0.0.2 to download at 256Kbit, even when it is the
only
> > > machine doing any downloading. I can affect this speed by changing
the
> > > $rate, but changing $ceil has no effect whatsoever.
> > The ceil will prevent 10.0.0.2 to download faster then 512 kbit. The
rate
> > will say how much 10.0.0.2 can download compare to the other classes (so
the
> > other lines are also relevant :).
>
> No Stef,
> the rate is really measured - it is used as source for DRR weight
> (here it is used relative to other classes) and to see whether we
> need to borrow from parent - here absolute value matters.
> So that the example above should work and give 512k.
>
> Gavin, did you tried with only these classes present ? (to have
> maximaly simplified configuration which exhibits it).
> If yes and it really does only 256k then post
> tc -s {qdisc,class} show dev ethXX outputs ... as usual
> devik
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-04-05 11:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 8:19 [LARTC] htb ceiling Gavin
2002-04-05 8:42 ` Stef Coene
2002-04-05 9:01 ` Gavin
2002-04-05 10:40 ` Martin Devera
2002-04-05 11:58 ` Gavin [this message]
2002-04-05 12:10 ` Martin Devera
2002-04-05 12:26 ` Stef Coene
2002-04-05 12:26 ` Stef Coene
2002-04-05 12:41 ` Gavin
2002-04-05 13:09 ` Martin Devera
2002-04-05 15:52 ` Stef Coene
2002-04-07 17:52 ` Gavin
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=marc-lartc-101800796732146@msgid-missing \
--to=gavin@raha.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.