Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] capacity estimator is more than a bit off
Date: Fri, 20 Nov 2015 19:50:51 +0200	[thread overview]
Message-ID: <CAJq5cE0OXBu6M+vwomv-WpRF1Voq6GBHiCYDNGyNTQsQc3pO2Q@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5e6KxN+oM9pOqm_2WAOFyKpH+Q6JPAepysz=r73GZzdQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 323 bytes --]

The capacity estimator operates on the incoming traffic, and is meant for
use with variable capacity links in ingress mode.  It doesn't measure the
average throughput.

The autorate_ingress option causes the shaper to track the estimate with a
slight scale down.  I find it useful for 3G, less so on 4G.

- Jonathan Morton

[-- Attachment #2: Type: text/html, Size: 388 bytes --]

      reply	other threads:[~2015-11-20 17:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 12:07 Dave Taht
2015-11-20 17:50 ` Jonathan Morton [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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJq5cE0OXBu6M+vwomv-WpRF1Voq6GBHiCYDNGyNTQsQc3pO2Q@mail.gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@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