All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank v Waveren <fvw.lartc@var.cx>
To: lartc@vger.kernel.org
Subject: [LARTC] a simple setup with tbf and prio?
Date: Mon, 14 Apr 2003 22:06:27 +0000	[thread overview]
Message-ID: <marc-lartc-105035807108856@msgid-missing> (raw)

I'm trying to make a fairly average setup, I want to limit eth1 to
100kbit, and then prioritize things like ACK's and interactive traffic.

All the scripts I see do this with CBQ, however given the description
of it in the HOWTO, I think I'd be much happier having the limiting
done by a TBF. So what I'd like is to have the root qdisc be TBF, and
put a PRIO qdisc under this. However, from what I understand, I can't
put anything as a child under a TBF, not even a single other qdisc
because it's classless. Why is this? The concept of having a bandwidth
limiting qdisc as the root and putting prio queues under that makes
sense right?

Also, in the trivia section: Why won't the PRIO qdisc allow me to set
less than 2 bands?

-- 
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/

             reply	other threads:[~2003-04-14 22:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14 22:06 Frank v Waveren [this message]
2003-04-15  0:31 ` [LARTC] a simple setup with tbf and prio? 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
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-105035807108856@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.