All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Rompf <srompf@isg.de>
To: lartc@vger.kernel.org
Subject: [LARTC] HTB not that exact
Date: Thu, 06 Dec 2001 19:28:07 +0000	[thread overview]
Message-ID: <marc-lartc-100766696815760@msgid-missing> (raw)

Hi,

I'm experimenting using the HTB queueing discipline for traffic shaping.
However, it is not really exact. Currently, I try this setup:

tc qdisc add dev eth0 root handle 1: htb default 3

tc class add dev eth0 parent 1: classid 1:1 htb rate 20Mbit burst 4kB
tc qdisc add dev eth0 parent 1:1 sfq

tc class add dev eth0 parent 1: classid 1:2 htb rate 3Mbit burst 2kB
tc qdisc add dev eth0 parent 1:2 sfq

tc class add dev eth0 parent 1: classid 1:3 htb rate 77Mbit burst 150kB
tc qdisc add dev eth0 parent 1:3 sfq

tc filter add dev eth0 parent 1:0 prio 7 protocol ip handle 1 fw classid
1:1
tc filter add dev eth0 parent 1:0 prio 7 protocol ip handle 2 fw classid
1:2

/usr/local/sbin/iptables -t mangle -F OUTPUT
/usr/local/sbin/iptables -t mangle -A OUTPUT -p tcp --dport 9021 -j MARK
--set-mark 1
/usr/local/sbin/iptables -t mangle -A OUTPUT -p tcp --dport 9022:9023 -j
MARK --set-mark 2

The network adaptor is connected to a 100MBit switch. When testing with
netio, I can send up to 370kB/sec through class 1:2 and up to 2,4MB/sec
via class 1:1, both measured by one/multiple instances of netio and the
rate output of "tc -s class dev eth0". This effect occurs with Linux
2.4.16,  kernel either compiled with HZ set to 100 or 1024, and of
course independant of the filter type used. During the tests, no packets
need to be dropped, htb just delays.

Output when two netio instances are sending to class 1:2 for some time:

root@barkeeper /root/ >tc -s class list dev eth0
[...]

class htb 1:2 root leaf 800e: prio 0 rate 3Mbit ceil 3Mbit burst 2Kb
cburst 2Kb
 Sent 236734498 bytes 156441 pkts (dropped 0, overlimits 301823)
 rate 378286bps 250pps backlog 44p
 lended: 156397 borrowed: 0 giants: 0 injects: 0
 tokens: -3714 ctokens: -3714

[...]


tbf seems not to be able to do exact rate limiting, too. Anything wrong
in my configuration, or am I just taking false statistics?

Stefan

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

             reply	other threads:[~2001-12-06 19:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-06 19:28 Stefan Rompf [this message]
2001-12-06 19:48 ` [LARTC] HTB not that exact bert hubert
2001-12-06 20:33 ` Daniel Ryczek
2001-12-06 21:35 ` Stefan Rompf
2001-12-07 11:46 ` david
2001-12-07 16:57 ` Sami Farin
2001-12-08  8:51 ` Martin Devera
2001-12-08 11:52 ` bert hubert
2001-12-08 11:53 ` bert hubert
2001-12-08 15:18 ` devik

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-100766696815760@msgid-missing \
    --to=srompf@isg.de \
    --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.