From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB - sharing bandwidth
Date: Wed, 17 Sep 2003 17:58:23 +0000 [thread overview]
Message-ID: <marc-lartc-106382172731592@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106378151913142@msgid-missing>
On Wednesday 17 September 2003 08:50, Vladimir Trebicky wrote:
> Hi,
>
> What will happen if I set my htb this way:
>
> 1:1 - 512Kbps
>
> |\
> | \--1:10 - 256Kbps ceil 512Kbps
>
> \
> \---1:20 - 256Kbps ceil 512Kbps
>
> If 1:10 will have all the bandwidth, will also 1:20 have good
> latency, when it starts pinging?
>
> How much is burst important in this case?
Not important. Your ping will be bigger then the minimal burst.
You can get better responses if you lower the quantum.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-09-17 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 6:50 [LARTC] HTB - sharing bandwidth Vladimir Trebicky
2003-09-17 17:58 ` Stef Coene [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=marc-lartc-106382172731592@msgid-missing \
--to=stef.coene@docum.org \
--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.