From: Aaron Wood <woody77@gmail.com>
To: Michael Yartys <michael.yartys@protonmail.com>
Cc: Rich Brown <richb.hanover@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Robert X. Cringley: Wi-Fi 6 & Bufferbloat
Date: Mon, 8 Feb 2021 09:49:29 -0800 [thread overview]
Message-ID: <CALQXh-P4=2APP4EC2_qSsdxBYHP6pHo=KAPtkmJ3hO3cwtgkLg@mail.gmail.com> (raw)
In-Reply-To: <lDyO3M7dvLFwLrTHdhbH6s37YTw7B12ZrJU0h9VERLrtlCPJslkb0PdxPocWKBkFaulPOlfJQGjzRNTciJ0bao2SFpV5JvOKGRAFCHFmT1U=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1606 bytes --]
I'm continually frustrated that my cable headend appears to be using DOCSIS
3.1 for downstream, and 3.0 for upstream. Which means my Arris SB8200
isn't using PIE, but the standard FIFO (Gigabit down, 35Mbps up).
Cake to the rescue. With a celeron based router (x86-64), I'm hitting
line-rate with cake on ingress. But it's all necessary to get things to
where they should be from Comcast. I was hoping that the upgrade a to
DOCSIS 3.1 modem would get them to provision it for PIE, but apparently not.
My understanding is that all the Google Wifi units have airtime fairness
and fq_codel. But that doesn't help if the ISP is bloated. It sounds like
Eero may be using HTB / Cake?
On Mon, Feb 8, 2021 at 7:08 AM Michael Yartys via Bloat <
bloat@lists.bufferbloat.net> wrote:
> This is from the article: "Google Wi-Fi, and especially Nest, are
> terrible."
>
> I thought Google was one of the companies that really cared about this
> issue in their router products, at least the mesh stuff.
>
> Michael
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>
> On Monday, February 8th, 2021 at 14:43, Rich Brown <
> richb.hanover@gmail.com> wrote:
>
> > Once again, Cringely waves the bufferbloat flag...
> >
> > https://betanews.com/2021/02/05/wi-fi-6-is-a-bust-bufferbloat/
> >
> > Bloat mailing list
> >
> > Bloat@lists.bufferbloat.net
> >
> > https://lists.bufferbloat.net/listinfo/bloat
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 2584 bytes --]
prev parent reply other threads:[~2021-02-08 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 13:43 Rich Brown
2021-02-08 15:08 ` Michael Yartys
2021-02-08 17:49 ` Aaron Wood [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='CALQXh-P4=2APP4EC2_qSsdxBYHP6pHo=KAPtkmJ3hO3cwtgkLg@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=michael.yartys@protonmail.com \
--cc=richb.hanover@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