From: Catalin Bucur <cata@geniusnet.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] total bandwidth ocupied
Date: Mon, 16 Dec 2002 17:06:17 +0000 [thread overview]
Message-ID: <marc-lartc-104005852514094@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104000531807331@msgid-missing>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Adi Nugroho wrote:
| Dear sir/madam,
|
| I discover that bandwidth usage which is limited using htb is about 5
to 10%
| higher than the rate/ceil we set, if we monitor it using iptraf.
|
| I become more confused since I saw, the grafic in HTB homepage are
also show
| more bandwidth than the setting.
|
| My question is:
| * what is the exac value of this over bandwidth?
It depends of burst and cburst values that you (or tc) set. In Devik's
user guide says: "Latest tc tool will compute and set the smallest
possible burst when it is not specified". This means:
minimal_burst=max_rate*timer_resolution
So, for 2Mbit bandwidth on i386, minimal_burst=2Mbit*10ms kbit. This
says the theory, but in real world I saw that this minimal_burst
calculated by tc could be up to 64kbit. Am I missing something?
| * how to make the bandwidth are limited exacly at "x" kbps?
Set a lower value for ceil and a value for cburst thus:
ceil+cburst=limited_bandwidth
- --
Catalin Bucur mailto:cata@geniusnet.ro
NOC @ Genius Network SRL - Galati - Romania
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9/ggIpDe20wwI9oIRApcqAJ94Z53bvrGpAvCUVPO8mmI3eHIV2gCfcwXK
pALs5TiT9dbZf42GNtVBHOc=JRkQ
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-12-16 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 2:25 [LARTC] total bandwidth ocupied Adi Nugroho
2002-12-16 10:41 ` Stef Coene
2002-12-16 17:06 ` Catalin Bucur [this message]
2002-12-17 4:12 ` Adi Nugroho
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-104005852514094@msgid-missing \
--to=cata@geniusnet.ro \
--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.