From: Frank v Waveren <fvw.lartc@var.cx>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] a simple setup with tbf and prio?
Date: Tue, 15 Apr 2003 03:39:46 +0000 [thread overview]
Message-ID: <marc-lartc-105037810822287@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105035807108856@msgid-missing>
On Mon, Apr 14, 2003 at 09:56:19PM -0500, Martin A. Brown wrote:
> Hmmmm.....clearly I must have failed to explain something.
> [snip]
> TBF, as a classless qdisc, can only be a terminal qdisc. That makes it
> far less complex than CBQ, which can support an arbitrary number of nested
> classes.
Yes ok, I got that bit. I was merely wondering why TBF wasn't made
classful, like HTB is. Is there a fundamental reason why you couldn't
have a TBF that's classful?
> And one other note--it sounds like you want to use "tc filter" commands to
> prioritize ACKs and other interactive traffic. In order to use "tc
> filter" commands (classification), you need to have separate classes into
> which to classify your traffic. TBF provides no classes, so you can't
> classify!
That's why I wanted to add a prio qdisc under it.
--
Frank v Waveren Fingerprint: 21A7 C7F3
fvw@[var.cx|stack.nl|chello.nl] ICQ#10074100 1FF3 47FF 545C CB53
Public key: hkp://wwwkeys.pgp.net/fvw@var.cx 7BD9 09C0 3AC1 6DF2
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-04-15 3:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 22:06 [LARTC] a simple setup with tbf and prio? Frank v Waveren
2003-04-15 0:31 ` Martin A. Brown
2003-04-15 1:04 ` Frank v Waveren
2003-04-15 1:48 ` Martin A. Brown
2003-04-15 1:51 ` Frank v Waveren
2003-04-15 2:56 ` Martin A. Brown
2003-04-15 3:39 ` Frank v Waveren [this message]
2003-04-15 4:27 ` Martin A. Brown
2003-04-15 5:59 ` Frank v Waveren
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-105037810822287@msgid-missing \
--to=fvw.lartc@var.cx \
--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.