From: "Bob Puff" <bob@nleaudio.com>
To: lartc@vger.kernel.org
Subject: [LARTC] tc statistics
Date: Mon, 12 Feb 2007 15:49:20 +0000 [thread overview]
Message-ID: <20070212154516.M3349@nleaudio.com> (raw)
In-Reply-To: <marc-lartc-99115393524655@msgid-missing>
Hi Gang,
I'm still experiencing some bandwidth starvation with my script (below), so I
decided to look at the statistics by using:
tc -s qdisc show dev eth0 (where eth0 is the interface I'm trying to
rate-limit outbound packets)
I get, for example:
qdisc sfq 21: quantum 1514b perturb 10sec
Sent 133527926 bytes 413260 pkts (dropped 0, overlimits 0)
qdisc sfq 20: quantum 1514b perturb 10sec
Sent 42622473 bytes 184396 pkts (dropped 0, overlimits 0)
qdisc htb 1: r2q 10 default 21 direct_packets_stat 0
Sent 176150399 bytes 597656 pkts (dropped 0, overlimits 137379)
On first appearance, I would think this is telling me that the overall
limiting is kicking in, and I'm not limiting specifically in the class 21
(which is where I want the limiting).
Here's my script:
tc qdisc del dev eth0 root
tc qdisc add dev eth0 root handle 1: htb default 21
tc class add dev eth0 parent 1: classid 1:1 htb rate 370kbit
tc class add dev eth0 parent 1:1 classid 1:20 htb prio 0 rate 100kbit
tc class add dev eth0 parent 1:1 classid 1:21 htb prio 1 rate 200kbit ceil 370kbit
tc qdisc add dev eth0 parent 1:20 handle 20: sfq perturb 10
tc qdisc add dev eth0 parent 1:21 handle 21: sfq perturb 10
# Set high priority for a certain destination IP address:
tc filter add dev eth0 parent 1:0 protocol ip prio 0 u32 \
match ip dst 147.135.2.0/24 flowid 1:20
# Set high priority for <64 byte packets:
tc filter add dev eth0 parent 1:0 protocol ip prio 0 u32 \
match ip protocol 6 0xff \
match u8 0x05 0x0f at 0 \
match u16 0x0000 0xffc0 at 2 \
match u8 0x10 0xff at 33 \
flowid 1:20
# Set high priority for ICMP packets:
tc filter add dev eth0 parent 1:0 protocol ip prio 0 u32 \
match ip protocol 1 0xff \
flowid 1:20
# Set high priority for UDP packets (hopefully all VOIP!):
tc filter add dev eth0 parent 1:0 protocol ip prio 0 u32 \
match ip protocol 17 0xff \
flowid 1:20
Am I reading this incorrectly?
Bob
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-02-12 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 16:41 [LARTC] tc statistics Serguei I. Ivantsov
2001-07-03 16:56 ` [LARTC] TC statistics Nayak, Ramakrishna
2001-07-03 18:31 ` xplorer
2001-07-03 20:11 ` Nayak, Ramakrishna
2003-07-02 12:44 ` [LARTC] tc statistics Joerg Hartmann
2003-07-02 13:08 ` Simon Stemplinger
2007-02-12 15:49 ` Bob Puff [this message]
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=20070212154516.M3349@nleaudio.com \
--to=bob@nleaudio.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.