From: Walter Haidinger <walter.haidinger@gmx.at>
To: lartc@vger.kernel.org
Subject: [LARTC] htb attached to prio: makes sense?
Date: Wed, 23 Oct 2002 18:33:18 +0000 [thread overview]
Message-ID: <marc-lartc-103539807401269@msgid-missing> (raw)
Hi!
Does it make sense to create a prio qdisc and attach an
htb qdisc to it? I'm thinking of a configuration like:
root
|
+----- prio 1: -----+
| | |
1:1 1:2 1:3
| | |
sfq 11: htb 12: sfq 13:
|
+-------- 12:1 ---------+
| / | \ |
100: 101: 102: 103: 104: all sfq qdiscs
Really high priority traffic (VoIP) should go to 11:,
normal traffic (and bandwidth limited) to 101:-104:,
low priority traffic (which may starve) to 13:.
Q1: Is this really neccessary or is HTB alone sufficient
(i.e. attaching 12: to the root qdisc) by setting
proper priorities to 100:-104: ?
Q2: Do I attach all filters to 1: or should I attach
to 1: and 12: as required?
Q3: What about performance with an hierarchy like that?
Will this be an issue?
Regards, Walter
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-10-23 18:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-103539807401269@msgid-missing \
--to=walter.haidinger@gmx.at \
--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.