From: Dave Taht <dave.taht@gmail.com>
To: Aaron Wood <woody77@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Equivocal results with using 3.10.28-14
Date: Mon, 24 Feb 2014 11:47:31 -0500 [thread overview]
Message-ID: <CAA93jw7wOQxRjrAaXYGRc+zoA5STyfB-HEcj7AqBp6Vq7Lp1Sw@mail.gmail.com> (raw)
In-Reply-To: <CALQXh-O807W25S+DSL3+Sj9xv04XUavB6_B6PfVjnbobLNe55g@mail.gmail.com>
On Mon, Feb 24, 2014 at 11:38 AM, Aaron Wood <woody77@gmail.com> wrote:
> Rich,
>
> One thing that helped considerably on my my DSL link (21000/1200), was
> turning on the Link Layer Adaptation. With that, and efq_codel, I've been
> very happy with the (nearly non-existent) latency. Yeah, I lost a couple
> percent off the top, but the behavior is better. Although I was starting
> from a much better base given that Free.fr's DSL modems already using either
> fq_codel or RED (I'm not sure the specifics, but I think Dave Taht's gotten
> them from Free.fr in the past).
Free deployed fq_codel on the revolution V6 box 1.5 years back. They
found it necessary to fiddle with the target, and shared with me
nearly all the details of their setup
and their formula for target, which I have embedded here:
http://snapon.lab.bufferbloat.net/~d/draft-taht-home-gateway-best-practices-00.html
despite testing a lot on your line we didn't do much better than they...
> Dave, the 40ms target is the buffer latency target? or how often the drop
> rates are recomputed?
It is the starting point for the drop scheduler to start thinking
about dropping some packets.
> or how often the drop
> rates are recomputed?
That's a RED or PIE -thinking way of looking at the problem,
recomputing a random number across a fixed interval.
the drop rates in codel are computed on a decreasing interval based on
a invsqrt control law that is much smoother than pie or red.
>
> -Aaron
>
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2014-02-24 16:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 14:36 Rich Brown
2014-02-24 14:56 ` Aaron Wood
2014-02-25 13:09 ` Rich Brown
2014-02-25 13:37 ` Sebastian Moeller
2014-02-25 15:54 ` Dave Taht
2014-02-25 16:29 ` Sebastian Moeller
2014-02-24 15:24 ` Fred Stratton
2014-02-24 22:02 ` Sebastian Moeller
2014-02-24 15:51 ` Dave Taht
2014-02-24 16:14 ` Dave Taht
2014-02-24 16:38 ` Aaron Wood
2014-02-24 16:47 ` Dave Taht [this message]
2014-02-24 21:54 ` Sebastian Moeller
2014-02-24 22:40 ` Sebastian Moeller
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7wOQxRjrAaXYGRc+zoA5STyfB-HEcj7AqBp6Vq7Lp1Sw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=woody77@gmail.com \
/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