From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Explanation reqd. for few (more than few!) concepts in TC <long>
Date: Wed, 29 Oct 2003 18:59:49 +0000 [thread overview]
Message-ID: <marc-lartc-106745418905582@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106732522922215@msgid-missing>
On Wednesday 29 October 2003 16:02, Suraj Shankar wrote:
> > But the leaf class only contains the traffic and can
> > not send them. To do so,
> > you need to add a qdisc to that class. It's the
> > qdisc that will send the
> > packets. This can be a class-full qdisc so you can
>
> now, if you are saying a class differs from a qdisc in
> that it cannot send out packets and qdisc can ... i
> think that is not perfectly true, in that, if a fifo
> qdisc was attached as a child to a classful qdisc (say
> cbq) the fifo qdisc will not be able to send packets
> out directly, it has to dequeue to the parent and only
> the root can dequeue-out.
That's even confusing for me. I just ignore that part :(
> which (size of the packet) could vary, right?
> this would then lead to a dynamically sized queue, is
> this how it works?
Yes, you can stor a a number of packets in a pfifo. So the total queue length
(in bytes) can vary.
> > That's a difficult one, because YOU have to be the
> > bottleneck to get some good
> > shaping results. You can try the htb or the cbq
> > qdisc and take a higher ceil
> > then your link. You will not be the bottleneck and
> > loose some control.
>
> okey, so can you please tell me, if I fail to be the
> bottleneck, what maximum would happen ... IMO, I could
> carry on shaping but not for that extra few bytes, now
> available, right?
Most modems have a hugh queue to speed up downloads. But that queue can kill
the shaping you did. So you have to be sure the queue is never full. And
the only thing to do so is to never send more data then the modem can handle.
So you have to make sure YOU are the bottleneck.
> > If you have a bounded class, the ceil is the rate.
> > If it's not bounded, the
> > ceil will be the rate of a bounded parent class.
> 'ceil' IMHO, is a little different from 'cell', that
> the lartc howto talks about.
What part of the lartc howto ?
> > Just take some example tc commands and copy the
> > parameters you don't know.
> > The only parameters you have to change is rate and
> > weight.
> yeah, but the lartc howto talks about more ... so was
> wondering!
One of the reasons why I like htb is you don't need these confusing options.
And htb don't rely on the nic hardware to calculate the actual rate.
> > Do you mean the wrr qdisc? See the homepage of the
> > wrr qdisc.
>
> oops, I am sorry I meant according to the lartc howto,
> there are few WRR parameters that need to be set for
> CBQ!?
Ah the WRR schedule. I think one of these parameters is the weight. Just
take weight = rate / 10.
> IMHO, the root qdisc (by default) is a pfifo_fast
> (classless) qdisc ... which means if want a classful
> qdisc you would need to replace the default qdisc.
> By "replace", I mean attach it to root ... which then
> follows all packets 'enter here' ... which then gets
> me back to my original Q!
> have been to your site ... went back today ... but
> couldn't find pointers to my confusion.
If you add a class qdisc as the root qdisc, all packets are queued in the
class less qdisc and processed. So you don't need a filter.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
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-10-29 18:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 7:06 [LARTC] Explanation reqd. for few (more than few!) concepts in TC <long> Suraj Shankar
2003-10-28 18:08 ` Stef Coene
2003-10-28 18:08 ` Damjan
2003-10-29 14:23 ` Suraj Shankar
2003-10-29 15:02 ` Suraj Shankar
2003-10-29 15:07 ` Suraj Shankar
2003-10-29 18:41 ` Stef Coene
2003-10-29 18:59 ` Stef Coene [this message]
2003-10-30 5:54 ` Suraj Shankar
2003-10-30 6:10 ` Suraj Shankar
2003-10-30 10:38 ` Stef Coene
2003-10-30 10:43 ` Stef Coene
2003-10-31 7:23 ` Suraj Shankar
2003-10-31 9:47 ` 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-106745418905582@msgid-missing \
--to=stef.coene@docum.org \
--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.