From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Tianhe <ptq008@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Does employing a AQM on the home router also solve bufferbloat between home router and upstream devices?
Date: Tue, 2 Jun 2020 14:28:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.2006021426430.29463@uplift.swm.pp.se> (raw)
In-Reply-To: <CAKomtWR0+s_uqVUxcg37DuUjFpse3p6uyetwcfU4omcudFLOvg@mail.gmail.com>
On Tue, 2 Jun 2020, Tianhe wrote:
> What does it mean?
What I do is that on my WAN, I do bidirectional shaping/AQM at 90% of the
ISP configured rate, meaning buffering will generally be done in my device
instead of the ISP device, and my device has proper AQM so I have no
bufferbloat.
This is not perfect but it works well enough to make a big difference for
all normal use-cases.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2020-06-02 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 2:49 Tianhe
2020-06-02 2:58 ` David Lang
2020-06-02 12:28 ` Mikael Abrahamsson [this message]
2020-06-02 15:45 ` Dave Taht
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=alpine.DEB.2.20.2006021426430.29463@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bloat@lists.bufferbloat.net \
--cc=ptq008@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