From: Thomas Bushnell BSG <tb@becket.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] elementary usage clamping
Date: Wed, 06 Jun 2007 19:28:21 +0000 [thread overview]
Message-ID: <1181158101.24243.14.camel@localhost> (raw)
In-Reply-To: <1181104629.22239.25.camel@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 997 bytes --]
On Wed, 2007-06-06 at 12:42 -0300, Marco Aurelio wrote:
> use the HTB wondershaper that can be found at lartc.org
Thanks for your reply. I looked at wondershaper, and I could not tell
from the documentation whether it actually limited the rate of packets
transmitted, and policed incoming packets, in a reliable fashion.
In other words, all the documentation I see is written as if it is
addressing the case of a residential customer with a bandwidth-limited
connection (cable modem, say), that has large queues, and arranges to
shape on the box instead of on the connection's queues, allowing for
better and more sensitive control.
But it still seemed (from what I read) as if it tries to keep the pipe
as full as possible, merely reordering packets carefully, in which case
I'm sure to lose, because I *don't want* the pipe as full as possible; I
want to dribble bits out the pipe to conform to the pricing I have
agreed with my ISP.
Am I missing something?
Thomas
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-06-06 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 4:37 [LARTC] elementary usage clamping Thomas Bushnell BSG
2007-06-06 15:42 ` Marco Aurelio
2007-06-06 19:28 ` Thomas Bushnell BSG [this message]
2007-06-06 20:58 ` Marco Aurelio
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=1181158101.24243.14.camel@localhost \
--to=tb@becket.net \
--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.