From: Jonathan Morton <chromatix99@gmail.com>
To: Benjamin Cronce <bcronce@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] No backpressure "shaper"+AQM
Date: Tue, 24 Jul 2018 23:33:45 +0300 [thread overview]
Message-ID: <BC2B5A6E-8698-4973-B04A-9E0EA81C0755@gmail.com> (raw)
In-Reply-To: <CAJ_ENFG7X9Rpxvg6nxEoZ3+hD1tcNx0FAL3C9T40F=zEeEf-DQ@mail.gmail.com>
> On 24 Jul, 2018, at 11:11 pm, Benjamin Cronce <bcronce@gmail.com> wrote:
>
> The problem that I'm getting is by adding my own shaping, a measurable amount of the benefit of their AQM is lost. While I am limited to Codel, HFSC+Codel, or FairQ+Codel for now, I am actually doing a worse job of anti-bufferbloat than my ISP is. Fewer latency spices according to DSLReports.
We do know that applying SQM at the entry to the bottleneck link works much better than at the exit. It's a fundamental principle.
> That's when I thought of a backpressure-less AQM. Instead of having backpressure and measuring sojourn time as a function of how long it takes packets to get scheduled, predict an estimated sojourn time based on the observed rate of flow, but allow packets to immediately vacate the queue. The AQM would either mark ECN or drop the packet, but never delay the packet.
It's a reasonable idea. The key point is to use a deficit-mode scheduler/shaper, rather than the credit-mode ones that are common (mainly TBF/HTB). The latter are why you have such a big, uncontrolled burst from the ISP in the first place.
- Jonathan Morton
next prev parent reply other threads:[~2018-07-24 20:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 20:11 Benjamin Cronce
2018-07-24 20:33 ` Jonathan Morton [this message]
2018-07-24 20:48 ` Benjamin Cronce
2018-07-24 20:57 ` Dave Taht
2018-07-24 21:31 ` Dave Taht
2018-07-26 4:42 ` Dave Taht
2018-07-24 21:39 ` Benjamin Cronce
2018-07-24 21:44 ` Jonathan Morton
2018-07-24 21:58 ` Dave Taht
2018-07-24 22:12 ` Dave Taht
2018-07-25 0:11 ` Benjamin Cronce
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=BC2B5A6E-8698-4973-B04A-9E0EA81C0755@gmail.com \
--to=chromatix99@gmail.com \
--cc=bcronce@gmail.com \
--cc=bloat@lists.bufferbloat.net \
/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