From: Tomasz Wrona <twr@wp.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] Unshapeable traffic
Date: Tue, 03 May 2005 21:34:31 +0000 [thread overview]
Message-ID: <1294422007.20050503233431@wp.pl> (raw)
Hello,
Could somebody explain following issue ?
I set up htb class on outgoing external interface to shape p2p upload
traffic. I limited it to 4Mbit/s. I also set up iptables counters
chains in FORWARD chain to calculate traffic generated by p2p and
others.
While tc stats show that p2p shaping class keep defined 4Mbit traffic,
iptables counters show me that p2p traffic exceed traffic to 150% and
is about 6Mbit/s.
Ofcourse I revised twice all configs but no mistake found.
Whereas tc stats show some strange thing [class for p2p]:
class htb 1:18 parent 1:10 leaf 18: prio 3 rate 1500Kbit ceil 4Mbit burst 3474b cburst 6599b
Sent 17192942388 bytes 13525239 pkts (dropped 6936086, overlimits 0)
rate 501604bps 392pps backlog 90p
lended: 5070369 borrowed: 8454780 giants: 0
tokens: -4830 ctokens: -14550
I mean that dropped packets is about half of total sent pkts.
So I realize that's why iptables counters, which are "before" outgoing
traffic shaping, show just 6Mbit [100%+50%(dropped) traffic] instead
of defined 4Mbit.
OK, but why traffic doesn't slow down due to shaping and still assail
upload ? [I tried sqf and red qdisc attached to class].
Regards
tw
--
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2005-05-03 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 21:34 Tomasz Wrona [this message]
2005-05-03 22:51 ` [LARTC] Unshapeable traffic Andreas Klauer
2005-05-04 9:00 ` tw
2005-05-04 9:47 ` Andreas Klauer
2005-05-04 14:18 ` Andy Furniss
2005-05-04 14:58 ` Andy Furniss
2005-05-04 18:54 ` Andy Furniss
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=1294422007.20050503233431@wp.pl \
--to=twr@wp.pl \
--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.