All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] a simple setup with tbf and prio?
Date: Tue, 15 Apr 2003 02:56:19 +0000	[thread overview]
Message-ID: <marc-lartc-105037546120901@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105035807108856@msgid-missing>

Hmmmm.....clearly I must have failed to explain something.

 : > Does that illustrate for you why the top-level class should perform the
 : > shaping?
 :
 : Yeah, I got that. However I don't quite understand why TBF can't be
 : like CBQ, ie classful?

Let me try again.

The following qdiscs are classless:

  - tbf
  - pfifo_fast
  - sfq

The following qdiscs are classful:

  - prio
  - cbq
  - htb

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.

 : They both do the same thing (albeit in different ways), right?

Only in the most general way do they do the same thing.  Each qdisc
provides a set of parameters you can adjust to limit your bandwidth.
While CBQ is a fully-featured queuing discipline, TBF provides only
shaping capabilities.  Both CBQ and TBF are non-work-conserving qdiscs,
though--this is what you are looking for if you want to shape your
transmitted traffic.

Again, since you appear to want the non-work-conserving (shaping) features
of TBF in a classful form, you are well-advised to look at HTB.  HTB is an
implementation of TBF-style scheduling in a classful queuing discipline.

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!

-Martin

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com

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

  parent reply	other threads:[~2003-04-15  2:56 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 [this message]
2003-04-15  3:39 ` Frank v Waveren
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-105037546120901@msgid-missing \
    --to=mabrown-lartc@securepipe.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 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.