From: Patrick Van Acker <Patrick.VanAcker@student.kuleuven.ac.Be>
To: lartc@vger.kernel.org
Subject: [LARTC] taking a look at your cbq configuration?
Date: Wed, 16 Jan 2002 22:12:33 +0000 [thread overview]
Message-ID: <marc-lartc-101121921214503@msgid-missing> (raw)
Hello,
I read through the LARTC Howto, and I tried to setup a CBQ example from
Chapter 9.
tc qdisc add dev eth0 root handle 1: cbq bandwidth 10Mbit avpkt 1000 cell 8
tc class add dev eth0 parent 1: classid 1:1 cbq bandwidth 10Mbit rate
128kbit allot 1514 weight 12.8kbit prio 8 maxburst 20 avpkt 1000 bounded
tc class add dev eth0 parent 1:1 classid 1:10 cbq bandwidth 10Mbit rate
20kbit allot 1514 weight 2.0kbit prio 1 maxburst 20 avpkt 1000
tc class add dev eth0 parent 1:1 classid 1:20 cbq bandwidth 10Mbit rate
108kbit allot 1514 weight 10.8kbit prio 7 maxburst 20 avpkt 1000 bounded
tc qdisc add dev eth0 parent 1:10 sfq quantum 1514b perturb 10
tc qdisc add dev eth0 parent 1:20 sfq quantum 1514b perturb 10
tc filter add dev eth0 parent 1: protocol ip prio 20 u32 match ip sport 80
0xffff flowid 1:10
tc filter add dev eth0 parent 1: protocol ip prio 20 u32 match ip sport 25
0xffff flowid 1:20
However, it's not really working as I would expect.
I'd like to look at the exact configuration and some stats.
When I try
tc -s qdisc ls dev eth0
I get the following output:
qdisc cbq 1: rate 10Mbit (bounded,isolated) prio no-transmit
Sent 49318327 bytes 35920 pkts (dropped 0, overlimits 48978)
borrowed 0 overactions 0 avgidle 624 undertime 0
That's not I want: I'd like to see the different classes etc...
What am I doing wrong?
Regards,
Patrick
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next reply other threads:[~2002-01-16 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 22:12 Patrick Van Acker [this message]
2002-01-16 22:17 ` [LARTC] taking a look at your cbq configuration? Martin Devera
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-101121921214503@msgid-missing \
--to=patrick.vanacker@student.kuleuven.ac.be \
--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.