From: Aaron Wood <woody77@gmail.com>
To: "Wheelock, Ian" <ian.wheelock@commscope.com>
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>,
"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Really getting 1G out of ISP?
Date: Tue, 6 Jul 2021 15:40:14 -0700 [thread overview]
Message-ID: <CALQXh-Mxd5drM5=gbXKKCH-gUzv1Tx8n4y7=Vu9RCncSXhgKwQ@mail.gmail.com> (raw)
In-Reply-To: <MW4PR14MB479502847D70325BEA1E7A2C8F1B9@MW4PR14MB4795.namprd14.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2538 bytes --]
I'm sure it's present, as a capability. I just think it's not being used
(based on what I see for upstream bloat, which is >100ms without running
cake in the router).
On Tue, Jul 6, 2021 at 3:28 PM Wheelock, Ian <ian.wheelock@commscope.com>
wrote:
> The support for AQM (PIE) is mandatory in D3.1 modems regardless of the US
> mode in use (ie sc-qam (3.0) or ofdma (3.1) upstream), so it should be
> enabled.
>
> Get Outlook for Android <https://aka.ms/AAb9ysg>
>
> ------------------------------
> *From:* Bloat <bloat-bounces@lists.bufferbloat.net> on behalf of Aaron
> Wood <woody77@gmail.com>
> *Sent:* Tuesday, July 6, 2021 11:13:59 PM
> *To:* Livingood, Jason <Jason_Livingood@comcast.com>
> *Cc:* bloat@lists.bufferbloat.net <bloat@lists.bufferbloat.net>
> *Subject:* Re: [Bloat] Really getting 1G out of ISP?
>
> Are these in-flux changes to where the upstream split is why some modems
> report DOCSIS 3.1 downstream, but only 3.0 upstream? (and therefore aren't
> enabling AQM on the upstream?)
>
> -Aaron
>
> On Tue, Jun 22, 2021 at 4:04 PM Livingood, Jason via Bloat <
> bloat@lists.bufferbloat.net> wrote:
>
> > For DOCSIS the issue seems to be an unfortunate frequency split between
> up and downstream and use of lower efficiency coding schemes.
>
> Performance really takes a big step forward once a person has a D3.1 modem
> in their home, bringing OFDM and OFDMA as key advancements. Also in flux at
> the moment is where the upstream split is in cable networks, which are
> moving to mid-split or high-split designs that bring more upstream
> bandwidth. As well, over the past 18+ months, most cable networks have
> added substantially more upstream channels as well as performed quite a
> number of fiber node splits. And that is just below the physical layer
> stuff - there's also a lot of work at the software layer for modems and
> CMTSes that is quite interesting.
>
> JL
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
> <https://secure-web.cisco.com/12r7ZmOFM8ddVde0m7xhKWGeITD3XE3Ac8lYCXdEv60KV7M2dP0FljB3D2Drve2H_DrbajVB3m_YObAyONExbkEVq1hasawuiwj6gKBkdsagSp44rWmPbd3AYBB3T_gqXzw5lJilH-KCga_T694ymSPplZtkdJyEPAxcl4cd1elFxGzE2cKv0yWsHC3rCkJRNvkbEzEF6BPvlI8csBxJLA8k4wOTd-SpoSvQodsyQp6X8hBDSoo-OtpI1sVvNo84-c585IlURf4pCCiQfyHZvkBMmb_Ee0STbfr_Q3Jqc0qHqn6wOImpTw5-rG0JZktn8QFfPuZHvwR2eSVSXMyNBSg/https%3A%2F%2Flists.bufferbloat.net%2Flistinfo%2Fbloat>
>
>
[-- Attachment #2: Type: text/html, Size: 4444 bytes --]
next prev parent reply other threads:[~2021-07-06 22:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 4:00 Stephen Hemminger
2021-06-22 6:12 ` Sebastian Moeller
2021-06-22 7:44 ` Giuseppe De Luca
2021-07-06 22:31 ` Aaron Wood
2021-07-07 2:26 ` Dave Taht
2021-07-07 2:53 ` Aaron Wood
2021-07-08 19:56 ` [Bloat] [Cake] " David P. Reed
2021-06-22 23:04 ` [Bloat] " Livingood, Jason
2021-06-23 15:56 ` Stephen Hemminger
2021-07-06 22:13 ` Aaron Wood
2021-07-06 22:28 ` Wheelock, Ian
2021-07-06 22:40 ` Aaron Wood [this message]
2021-07-07 2:10 ` Dave Taht
2021-07-07 9:27 ` Wheelock, Ian
2021-07-07 16:17 ` Jonathan Morton
2021-07-07 16:24 ` Wheelock, Ian
2021-06-22 22:51 ` Livingood, Jason
2021-06-29 19:48 ` Stephen Hemminger
2021-06-29 20:09 ` Sebastian Moeller
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-Mxd5drM5=gbXKKCH-gUzv1Tx8n4y7=Vu9RCncSXhgKwQ@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=Jason_Livingood@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=ian.wheelock@commscope.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