Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Mihai Tanasescu <Mihai.Tanasescu@skyraven.pcnet.ro>
To: lartc@vger.kernel.org
Subject: [LARTC] IMQ htb question
Date: Mon, 28 Jun 2004 12:49:58 +0000	[thread overview]
Message-ID: <40E013F6.8040909@skyraven.pcnet.ro> (raw)

Hello,

I've just recently started to use IMQ and I got puzzled after seeing the 
imq usage example on the linuximq.net site:

It was something like this:

tc qdisc add dev imq0 handle 1: root htb default 1
tc class add dev imq0 parent 1: classid 1:1 htb rate 1mbit
tc qdisc add dev imq0 parent 1:1 handle 10: htb default 5
tc class add dev imq0 parent 10: classid 10:1 htb rate 256kbit burst 30k 
prio 1

and I tried the following (like in the classic htb examples from lartc) 
and it worked:

tc qdisc add dev imq0 handle 1: root htb default 99
tc class add dev imq0 parent 1: classid 1:1 htb rate 1mbit
tc class add dev imq0 parent 1:1 classid 1:10 htb rate 100kbit
tc class add dev imq0 parent 1:1 classid 1:99 htb rate  900kbit

tc qdisc add dev imq0 parent 1:10 handle 100 sfq perturb 10
tc qdiisc add dev imq0 parent 1:99 handle 9 sfq perturb 10

Can someone help me understand the first example and why would someone 
create a root qdisc that redirects all traffic to a class and then 
instead of attaching child classes to that class,  one would create a 
qdisc associated with that class and then attach the child classes to it.




_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2004-06-28 12:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-28 12:49 Mihai Tanasescu [this message]
2004-06-28 15:40 ` [LARTC] IMQ htb question Andre Correa

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=40E013F6.8040909@skyraven.pcnet.ro \
    --to=mihai.tanasescu@skyraven.pcnet.ro \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox