From: Stef Coene <stafke@iname.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] TBF question
Date: Thu, 17 May 2001 07:46:08 +0000 [thread overview]
Message-ID: <marc-lartc-99442749201860@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98982047809726@msgid-missing>
TBF uses internal 2 TBF control mechanism. One for the short burst and
one for a long time control. I think that buffer and limit contols ths
short burst and rate the long time traffic control. I putted it on my
TODO list to test it out.
Gery Kahn wrote:
>
> Who can explain parameter buffer and limit in TBF
>
> tc qdisc add dev eth1 parent 20:1 tbf rate 2Mbit buffer 30Kb/8 limit 15Kb
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
--
Stef
More QOS info : http://users.belgacom.net/staf/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-05-17 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-14 6:07 [LARTC] TBF question Gery Kahn
2001-05-17 7:46 ` Stef Coene
2001-05-17 7:46 ` Stef Coene [this message]
2001-05-17 13:46 ` Kurt Wagner
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-99442749201860@msgid-missing \
--to=stafke@iname.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.