From: Neal Cardwell <ncardwell@google.com>
To: Aaron Wood <woody77@gmail.com>
Cc: Simon Barber <simon@superduper.net>,
"starlink@lists.bufferbloat.net"
<starlink@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Of interest: Comcast AQM Paper
Date: Sat, 31 Jul 2021 18:55:53 -0400 [thread overview]
Message-ID: <CADVnQyk+DnCootU9bOZhX9PS2tAqXDc+wZB4djr6rQTVAcMm-Q@mail.gmail.com> (raw)
In-Reply-To: <CALQXh-OFGN2ehdxhBJ9g_b0jCL2kyVsdHYmxY8QxW14A6f23Wg@mail.gmail.com>
On Sat, Jul 31, 2021 at 3:27 PM Aaron Wood <woody77@gmail.com> wrote:
>
> If we see that AQM appears to be not functioning as expected
> for upstream connections on DOCSIS3.1, what's the right avenue
> for getting that resolved? (and does that only apply to the
> Comcast-owned, vs. customer-owned, modems?)
FWIW, from the paper it sounds like not all Comcast cable modems
had/have PIE, which enabled the A/B experiment:
"10. Latency Measurement Results
As explained earlier, for two variants of XB6 cable modem gateway,
upstream DOCSIS-PIE AQM was enabled on the CGM4140COM (experiment)
variant but was not available on the TG3482G (control) variant during
the measurement period. The TG3482G variant used a buffer control
configuration that predated AQM in DOCSIS."
neal
>
> On Sat, Jul 31, 2021 at 10:50 AM Simon Barber <simon@superduper.net> wrote:
>>
>> Awesome to hear that you are turning this on both upstream and downstream. Do you know if the wifi stacks in your home routers also have AQM?
>>
>> Simon
>>
>>
>> > On Jul 30, 2021, at 10:28 PM, Livingood, Jason via Bloat <bloat@lists.bufferbloat.net> wrote:
>> >
>> > FYI that I will be presenting a lightning talk at the IRTF MAPRG meeting today at 17:30 ET (https://datatracker.ietf.org/meeting/111/materials/agenda-111-maprg). The talk links to a just-published paper at https://arxiv.org/abs/2107.13968 (click PDF link in upper right of page) that will likely be of interest to these two lists.
>> >
>> > High-level: turning on AQM in the cable modem (upstream queue) took working latency from around 250 ms to between 15-30 ms, which is actually kind of cool. ;-) AQM is turned on in all of our CMTSes (downstream queue) and in DOCSIS 3.1 modems (upstream queue).
>> >
>> > Have a nice weekend,
>> > Jason
>> >
>> > _______________________________________________
>> > 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
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2021-07-31 22:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 21:28 Livingood, Jason
2021-07-31 17:50 ` Simon Barber
2021-07-31 19:26 ` Aaron Wood
2021-07-31 22:55 ` Neal Cardwell [this message]
2021-08-01 13:13 ` Michael Richardson
2021-08-01 20:13 ` Kenneth Porter
2021-08-01 20:28 ` Livingood, Jason
2021-08-01 21:00 ` Kenneth Porter
2021-08-05 17:37 ` [Bloat] [EXTERNAL] " Livingood, Jason
2021-08-01 20:20 [Bloat] " Livingood, Jason
2021-08-01 20:21 Livingood, Jason
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=CADVnQyk+DnCootU9bOZhX9PS2tAqXDc+wZB4djr6rQTVAcMm-Q@mail.gmail.com \
--to=ncardwell@google.com \
--cc=bloat@lists.bufferbloat.net \
--cc=simon@superduper.net \
--cc=starlink@lists.bufferbloat.net \
--cc=woody77@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