From: "Gerry Weaver" <gerryw@objectivedomain.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Need Clarification on TBF + (PRIO+SFQ)
Date: Mon, 15 Mar 2004 05:45:39 +0000 [thread overview]
Message-ID: <ILECICAFAJIIMPBBLMEAMEJGCPAA.gerryw@objectivedomain.com> (raw)
Hi All,
I need help to understand the proper order to create qdiscs. I'm trying to
do the following:
1. Use the TBF to slow a 100mb link to 3mb
2. Use PRIO to prioritize the traffic
3. Use SFQ to hand out bandwidth to each PRIO class fairly
Here's my question. What order should the qdiscs be in? For example:
ROOT->TBF->PRIO[1,2,3]->SFQ or ROOT->PRIO[1,2,3]->SFQ->TBF
Please forgive me if this is a stupid question. I'm a total newbie ;-).
Thanks in advance,
Gerry
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.576 / Virus Database: 365 - Release Date: 1/30/2004
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2004-03-15 5:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 5:45 Gerry Weaver [this message]
2004-03-15 9:35 ` [LARTC] Need Clarification on TBF + (PRIO+SFQ) Corey Hickey
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=ILECICAFAJIIMPBBLMEAMEJGCPAA.gerryw@objectivedomain.com \
--to=gerryw@objectivedomain.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.