From: Peter Rabbitson <rabbit@rabbit.us>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Unclarified issue
Date: Mon, 12 May 2003 21:08:02 +0000 [thread overview]
Message-ID: <marc-lartc-105277431329422@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105274679628578@msgid-missing>
So in other words if we define a cbq at 1:0 and then define a class 1:1, and DO NOT attach any qdiscs at parent 1:1,
all packets that went to 1:1 will be simply discarded?
P.S. Examples are fine but going down and getting dirty is way more fun :)
On Mon, May 12, 2003 at 09:18:48PM +0200, Stef Coene wrote:
> On Monday 12 May 2003 15:35, Peter Rabbitson wrote:
> > Hi all,
> > Just finished reading and re-reading the advanced routing how-to. This this
> > is marvelous!!! Thank you all that spent your time and devoted it to such a
> > great paper! However there is something that I am missing from the picture.
> > By default each interface is bundled with the pfifo_fast that prioritizes
> > the packets based on TOS. If for say we do this: # tc qdisc add dev eth0
> > root tbf rate 100kbit latency 100ms urst 2048 Do we actually lose the whole
> > point of TOS? Or there is stil an underlying filter somewhere in the kernel
> > that will take care of the TOS scheduling just like pfifo_fast did?
> You loose the TOS settings.
>
> > Also in the following example:
> > # tc qdisc add dev eth0 root handle 1: prio
> > We automatically create three handles 1:1 1:2 1:3, with the default
> > priomap. However what happens to traffic that goes down 1:1 if there is no
> > qdisc attached to it? Does it get dequeued right off the back or there is
> > again something similar to pfifo_fast waiting for it?
> There is always a qdisc responsible for sending the packets. If you add a
> prio qdisc, you also created 3 small fifo qdiscs for each class.
>
> If you want some example shaping scripts (mostly cbq and htb), you can go to
> docum.org.
>
> 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/
_______________________________________________
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-05-12 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 13:35 [LARTC] Unclarified issue Peter Rabbitson
2003-05-12 19:18 ` Stef Coene
2003-05-12 21:08 ` Peter Rabbitson [this message]
2003-05-13 17:13 ` Stef Coene
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-105277431329422@msgid-missing \
--to=rabbit@rabbit.us \
--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