From: Jesper Dangaard Brouer <hawk@comx.dk>
To: Florian Lohoff <f@zz.de>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Network latency experiments
Date: Fri, 25 Feb 2011 21:47:15 +0100 [thread overview]
Message-ID: <1298666835.28000.64.camel@traveldev.cxnet.dk> (raw)
In-Reply-To: <20110222092623.GA11764@pax.zz.de>
On Tue, 2011-02-22 at 10:26 +0100, Florian Lohoff wrote:
> I solved it with a "tc" htb with a 128kbit rate/ceil which is my
> upstream speed and a short queue (in the tc).
Please remember to used the option "linklayer adsl" plus the "overhead"
tc options when shaping on ADSL links. Or else you will loose queue
control due to the special ADSL linklayer (ATM) overhead properties.
Detailed info available on http://www.adsl-optimizer.dk.
--
Best regards
Jesper Brouer
ComX Networks A/S
Linux Network Kernel Developer
Cand. Scient Datalog / MSc.CS
Author of http://adsl-optimizer.dk
LinkedIn: http://www.linkedin.com/in/brouer
prev parent reply other threads:[~2011-02-25 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 23:27 Dan Siemon
2011-02-22 9:26 ` Florian Lohoff
2011-02-25 20:47 ` Jesper Dangaard Brouer [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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1298666835.28000.64.camel@traveldev.cxnet.dk \
--to=hawk@comx.dk \
--cc=bloat@lists.bufferbloat.net \
--cc=f@zz.de \
/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