From: Simon Barber <simon@superduper.net>
To: "Livingood, Jason" <Jason_Livingood@comcast.com>
Cc: "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:50:26 +0100 [thread overview]
Message-ID: <D521120A-0E1E-4F29-AE16-D54B8E345513@superduper.net> (raw)
In-Reply-To: <F6AF3855-2CCA-4843-A5AD-810CF09CE8BA@cable.comcast.com>
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
next prev parent reply other threads:[~2021-07-31 17:50 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 [this message]
2021-07-31 19:26 ` Aaron Wood
2021-07-31 22:55 ` Neal Cardwell
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=D521120A-0E1E-4F29-AE16-D54B8E345513@superduper.net \
--to=simon@superduper.net \
--cc=Jason_Livingood@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=starlink@lists.bufferbloat.net \
/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