From: Michal Kustosik <kustosz@veb.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] cbq and htb working together...
Date: Thu, 13 Feb 2003 21:55:41 +0000 [thread overview]
Message-ID: <marc-lartc-104517339118046@msgid-missing> (raw)
Is it possible to use cbq and htb together on one dev?
something like this:
[...]
$TC qdisc add dev eth0 root handle 1:0 cbq bandwidth 100Mbit avpkt 1000
$TC class add dev eth0 parent 1:0 classid 1:10 cbq bandwidth 100Mbit \
rate 100Mbit weight 10Mbit prio 8 allot 1514 cell 8 maxburst 5 avpkt 1000 bounded
$TC qdisc add dev eth0 parent 1:10 htb default 100
$TC class add dev eth0 parent 1:10 classid 1:100 htb rate 128kbit ceil 128kbit prio 3
$TC class add dev eth0 parent 1:10 classid 1:200 htb rate 128kbit ceil 128kbit prio 2
$TC class add dev eth0 parent 1:10 classid 1:300 htb rate 128kbit ceil 128kbit prio 1
[...]
but it does't work :(
--
/kustosz
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-02-13 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 21:55 Michal Kustosik [this message]
2003-02-13 22:33 ` [LARTC] cbq and htb working together Stef Coene
2003-02-13 22:40 ` Michal Kustosik
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-104517339118046@msgid-missing \
--to=kustosz@veb.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.