From: Alexey Talikov <alexey_talikov@texlab.com.uz>
To: lartc@vger.kernel.org
Subject: Re: Re: [LARTC] a question about TBF
Date: Tue, 04 Jun 2002 04:36:08 +0000 [thread overview]
Message-ID: <marc-lartc-102316545210784@msgid-missing> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1252", Size: 2722 bytes --]
Read shapter
9.2.2.1. Parameters & usage in Advanced Routing HOWTO
mpu
A zero-sized packet does not use zero bandwidth. For ethernet, no packet uses less than 64 bytes.
The Minimum Packet Unit determines the minimal token usage for a packet
15.02.2000 8:37:10, Huang Xin Gang <hxgang@csnet4.cs.tsinghua.edu.cn> wrote:
>Alexey Talikov,hello!
>
>Thanks for your help!
>But my problem is still here.I found that if a packet is too short,the tick value which
corresponds to it in the "rtab" is zero.That means the packet doesn't consume any tokens when it's
being sent.
>
>Is my knowledge right?
>
>
>==== 2002-06-03 09:09:00 you wrote:===>
>>Increase your burst it value at list MTU i.e 1500 byte
>>
>>rate=ST*burst (ST system timer 100HZ for intel/amd 1024 for alpha)
>> rate
>>burst=------- and burst>MTU
>> ST
>>
>>See: Advanced routing HOWTO and for more details
>>Short Evaluation of Linux's TBF Queueing Discipline. Kurt Wagner 17 May 2001
>>
>>03.06.2002 7:27:30, Huang Xin Gang <hxgang@csnet4.cs.tsinghua.edu.cn> wrote:
>>
>>>LARTC£¬hello£¡
>>>
>>>I set the command following:
>>>
>>>tc qdisc add dev eth0 root tbf rate 100kbit latency 50ms burst 120
>>>
>>>and then I send flow with speed of 115.2kbit, and if all the packets sent is only 120bytes,the
>>above command is useless.
>>>
>>>I thinks because the time occupied when sent a packet only 120 bytes is 120*8/(100*1024)<10ms,
>>>but Linux system produces a tick every 10ms,so every time when a packet only 120 bytes
>>>is being sent, the "toks" equals to zero always, and this packet can be sent immediately.
>>>
>>>all the packets are sent immediately, then the speed is not limited to 100kbit.
>>>
>>>How can I deal with this problem?
>>>
>>>¡¡¡¡¡¡best regards!
>>>
>>>
>>>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Huang Xin Gang
>>>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡hxgang@csnet4.cs.tsinghua.edu.cn
>>>¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-06-03
>>>,\x04S
>>>f¢–)à–+-ü°\x11L)šŠYš?jya¶Ú?þf¢–f§vÏZž_æj)fj?åŠËbú?•ªíps–Lèm¶Ÿ?•ªírŠà
>>
>>-----------------------------------
>>mailto:alexey_talikov@texlab.com.uz
>>BR
>>Alexey Talikov
>>FORTEK
>>-----------------------------------
>
>= = = = = = = = = = = = = = = = = = = >
>
> best regards!
>
> Huang Xin Gang
> hxgang@csnet4.cs.tsinghua.edu.cn
> 2000-02-15
-----------------------------------
mailto:alexey_talikov@texlab.com.uz
BR
Alexey Talikov
FORTEK
-----------------------------------
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-06-04 4:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-102316545210784@msgid-missing \
--to=alexey_talikov@texlab.com.uz \
--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