From: Damion de Soto <damion@snapgear.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tbf token help
Date: Wed, 23 Jun 2004 00:01:35 +0000 [thread overview]
Message-ID: <40D8C85F.1020706@snapgear.com> (raw)
In-Reply-To: <200406211243.22474.mknific@siol.net>
Have you fully read:
http://lartc.org/howto/lartc.qdisc.classless.html#AEN691
?
most of it is explained in there.
> 1) What unit is token? Is "1 token = 1 byte" ?
> If this is so, then with rate=0.5mbit and HZ\x100 the bucket gets filled
> with 0,64kb (655 tokens) every 10ms?
1 token is one packet.
> 2) How much tokens are used for one packet (1500)?
1
> 3) And token unrelated question. Does packet droping alway ocurrs or
> it happens because of bad settings?
>
> I have applied this settings on 10mbit ethernet card:
> tc qdisc add dev eth1 root tbf rate 0.5mbit burst 5kb latency 70ms /
> peakrate 1mbit minburst 1540
>
> Result:
> qdisc tbf 8007: dev eth1 rate 512Kbit burst 5Kb/8 mpu 0b peakrate 1Mbit mtu
> 1539b/8 mpu 0b lat 68.4ms
> Sent 1284481 bytes 852 pkts (dropped 48, overlimits 1743)
Packet dropping happens when too much data is coming in.
See the explanation in the link above.
regards,
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Damion de Soto - Software Engineer email: damion@snapgear.com
SnapGear - A CyberGuard Company --- ph: +61 7 3435 2809
| Custom Embedded Solutions fax: +61 7 3891 3630
| and Security Appliances web: http://www.snapgear.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--- Free Embedded Linux Distro at http://www.snapgear.org ---
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-06-23 0:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 10:43 [LARTC] tbf token help mknific
2004-06-23 0:01 ` Damion de Soto [this message]
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=40D8C85F.1020706@snapgear.com \
--to=damion@snapgear.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.