From: Dave Taht <dave.taht@gmail.com>
To: Tianhe <ptq008@gmail.com>
Cc: bloat <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 08:45:23 -0700 [thread overview]
Message-ID: <CAA93jw4yGiz6UA61SKxEO9HhrEEV=p6bko5=yMX_-MAE9NPb1A@mail.gmail.com> (raw)
In-Reply-To: <CAKomtWR0+s_uqVUxcg37DuUjFpse3p6uyetwcfU4omcudFLOvg@mail.gmail.com>
On Mon, Jun 1, 2020 at 7:49 PM Tianhe <ptq008@gmail.com> wrote:
>
> Hi there. I've read some materials from bufferbloat.net and other sites, trying to understand the problem as best as I can.
>
> And I have a question when reading this:
>
> From https://www.bufferbloat.net/projects/bloat/wiki/What_can_I_do_about_Bufferbloat/ , it says:
>
>> Once you fix it for your own network, it’ll stay fixed for all time, and you won’t be subject to changing practices at your ISP or other vendors.
Well, we should be less optimistic about "all time", nowadays, as
cable ISPs are adding oracles to dynamically change the amount of
bandwidth
you are configured as they overload individual segments. Evenroute is
monitoring "sag" which seems to happen on many dsl
backhauls.
>
> What does it mean?
>
> Does it mean that :
>
> if I employ a Smart Queue Management algorithms on my home router, it only solves the bufferbloat problem between my home devices (desktop, laptop ,cellphone) to my home router. But the buffers between my home router to upstream devices (my home router ---> modem ---> ISP routers/switches) , buffers between upstream devices, will still harm? So I only fix the bufferbloat problem on my own local network?
>
> or it mean that employing a Smart Queue Management algorithms on the home router also solve bufferbloat between home router and upstream devices?
>
> Thanks in advance.
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
prev parent reply other threads:[~2020-06-02 15:45 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
2020-06-02 15:45 ` Dave Taht [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='CAA93jw4yGiz6UA61SKxEO9HhrEEV=p6bko5=yMX_-MAE9NPb1A@mail.gmail.com' \
--to=dave.taht@gmail.com \
--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