From: L Rotger <lrotger@aircomp.aero>
To: lartc@vger.kernel.org
Subject: [LARTC] ceil, cburst, prio not working?
Date: Tue, 03 Aug 2004 10:05:38 +0000 [thread overview]
Message-ID: <410F6372.5000000@aircomp.aero> (raw)
Hi, I've been using htb fine to separate outgoing SMTP traffic from HTTP
traffic so sending big emails doesn't affect browsing. As long as ceil
= burst and the sum of all rates don't exceed the root class' rate all
is fine but when I incorporate ceil I would expect (from lartc howto)
that when other classes are idle the remaining bandwith would be
assigned in order of prio (I believe, again from howto that 0 is
highest) to other classes, which is not happening.
In particular, sending big test emails (with everything else idle) shows
that SMTP traffic never exceeds exactly 3kbps, even with ceil set at
9kbps. I measured the speed with iptraf. What am I doing wrong?
List of my classes. If you need more info, please let me know!
# tc class show dev eth2
class htb 1: root prio 0 rate 13312bit ceil 13312bit burst 1732b cburst 5Kb
class htb 1:20 root prio 7 rate 12bit ceil 12bit burst 1599b cburst 1599b
class htb 1:5 root prio 2 rate 13312bit ceil 13312bit burst 1732b cburst
1732b
class htb 1:6 root prio 3 rate 13312bit ceil 13312bit burst 1732b cburst
1732b
class htb 1:7 root prio 4 rate 4096bit ceil 4096bit burst 1639b cburst 5Kb
class htb 1:8 root prio 5 rate 3072bit ceil 9216bit burst 1629b cburst
1691b
class htb 1:9 root prio 6 rate 3072bit ceil 9216bit burst 1629b cburst
1691b
root class: 1:0
siblings: 1:5, 1:6, 1:7, 1:8, 1:9, 1:20
SMTP outgoing traffic goes out 1:8
1:20 is the default so all non-specifically filtered traffic goes out
slowly (rate is 0.1kbit) so I know what's left to filter.
Thanks in advance!
L Rotger
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2004-08-03 10:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=410F6372.5000000@aircomp.aero \
--to=lrotger@aircomp.aero \
--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.