From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb qdiscs inside htb classes tree - possible side effects???
Date: Sun, 17 Aug 2003 18:13:35 +0000 [thread overview]
Message-ID: <marc-lartc-106114419505110@msgid-missing> (raw)
On Tuesday 12 August 2003 15:27, Robert Krycza³o wrote:
[big snip]
> My question is ... are there any problems lurking inside this idea
> compared to my previous setup. Does an extra qdisc (no rate, no ceil,
> no prio) change htb behaviour described on pages of docum.org,
> especially link sharing rules? Is there a catch or everything will
> work as expected?
The setup wih the extra qdiscs will work. But an extra qdisc means a bgger
box needed and higher delays.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-08-17 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-17 18:13 Stef Coene [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-12 13:27 [LARTC] htb qdiscs inside htb classes tree - possible side effects??? Robert Kryczało
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-106114419505110@msgid-missing \
--to=stef.coene@docum.org \
--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