From: "Sumit Pandya" <sumit@elitecore.com>
To: lartc@vger.kernel.org
Subject: [LARTC] exploring HTB
Date: Wed, 13 Feb 2002 14:54:36 +0000 [thread overview]
Message-ID: <marc-lartc-101361106601378@msgid-missing> (raw)
Hi All,
I have few queries in reference of HTB manuals on link
http://luxik.cdi.cz/~devik/qos/htb/htbman.htm.
1> Is "default" is must while attaching queue discipline HTB to device?
My observation for above question is, when I do following 4 command then I’
m able to reach to all hosts on eth1. But if I remove "default 12" from
second command then I cannot reach to hosts on eth1, but I can reach to the
host on other device (eth0, eth2). This occurs after I create extra class to
serve as the root (i.e. creating class having parent 1:1, 4th command)
tc qdisc del dev eth1 root
tc qdisc add dev eth1 root handle 1: htb default 12
tc class add dev eth1 parent 1: classid 1:1 htb rate 100kbps ceil 100kbps
burst 2k
tc class add dev eth1 parent 1:1 classid 1:11 htb rate 10kbps ceil 100kbps
burst 2k
tc class add dev eth1 parent 1:1 classid 1:12 htb rate 60kbps ceil 100kbps
burst 2k
Ya, this reachability can be restored only after delition of root class,
i.e. classid 1:1. I'm taking this as a feature but is it a bug?
2> Manual states that "... ... ... Now we can optionally attach queuing
disciplines to the leaf classes... ... ... tc qdisc add dev eth0 parent 1:10
handle 20: pfifo limit 5... ... ...". If I not going to do that still I'm
fine with my rule set, as written "optional". Then is there benefit or
payoff against this leaf-class?
3> A Small but nice document about Cross device sharing on link
http://luxik.cdi.cz/~devik/qos/htb/htbmeas1.htm. Can’t this limitation of
slot be increased?
4> It would be nice if someone help me by providing statistics over number
of queues and filter. What is maximum limit of these two for a PIII 700 with
256 MB RAM? How much maximum bandwidth can be shaped?
Thanks in Advance.
-- Sumit
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next reply other threads:[~2002-02-13 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 14:54 Sumit Pandya [this message]
2002-02-13 15:05 ` [LARTC] exploring HTB Stef Coene
2002-02-14 10:59 ` Martin Devera
2002-02-15 9:22 ` Sumit Pandya
2002-02-15 12:01 ` Martin Devera
2002-02-16 20:22 ` Don Cohen
2002-02-16 21:19 ` Martin Devera
2002-02-16 21:33 ` Don Cohen
2002-02-16 21:42 ` 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-101361106601378@msgid-missing \
--to=sumit@elitecore.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox