From: Suraj Shankar <su_raj_in@yahoo.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Explanation reqd. for few (more than few!) concepts in TC <long>
Date: Thu, 30 Oct 2003 06:10:59 +0000 [thread overview]
Message-ID: <marc-lartc-106749431711874@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106732522922215@msgid-missing>
Hi,
--- Stef Coene <stef.coene@docum.org> wrote:
> > 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.
yes! I understood something :) Thank you.
> > 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.
yes, I have a proof-of-concept! ... meaning wrote a
script that works but, waiting to take it 'live'.
> > 'ceil' IMHO, is a little different from 'cell',
> that
> > the lartc howto talks about.
> What part of the lartc howto ?
http://lartc.org/lartc.html#AEN939 ; the part that
lists parameters in CBQ ... was wondering how 'cell'
can be defined.
> > 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.
hmm, that's true.
> > 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.
okey, but how do I set it ...
Usage: ... cbq bandwidth BPS avpkt BYTES [ mpu BYTES ]
[ cell BYTES ] [ ewma LOG ]
...this is what tc...help says, there isn't a weight
parameter :(
> 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, I do really appreciate the time spent in trying
to help me. Thank you.
Warm Regards,
suraj.
__________________________________
Do you Yahoo!?
Exclusive Video Premiere - Britney Spears
http://launch.yahoo.com/promos/britneyspears/
_______________________________________________
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-30 6:10 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
2003-10-30 5:54 ` Suraj Shankar
2003-10-30 6:10 ` Suraj Shankar [this message]
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-106749431711874@msgid-missing \
--to=su_raj_in@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox