From: Dave Taht <dave.taht@gmail.com>
To: "aqm@ietf.org" <aqm@ietf.org>, bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Arris thoughts on bufferbloat in the CMTS
Date: Thu, 20 Feb 2014 15:36:49 -0500 [thread overview]
Message-ID: <CAA93jw5-xdM1xB0kQ9_ggSYEs8A8GB59-egdmJQJ+y0_yhsTcA@mail.gmail.com> (raw)
I finally got my SCTE proceedings today.
In there were a presentation and paper by Arris's CTO and several of
his senior engineers...
http://snapon.lab.bufferbloat.net/~d/trimfat/Cloonan_Paper.pdf
http://snapon.lab.bufferbloat.net/~d/trimfat/Cloonan_Presentation.pdf
There are some very good ideas and analysis in here, a nice
enhancement to SFQ easily implementable in hardware, and a new version
of RED, called "LRED".
In a first reading, there are a few things I quibble with (they missed
the SQF-like portion of fq_codel entirely, for example), but it is
really nice to have seen Jim's
paper go from "so-called" in 2011, to "seminal" in 2013.
These are worth reading thoroughly. I will wait until saturday to
comment further.
--
Dave Täht
reply other threads:[~2014-02-20 20:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw5-xdM1xB0kQ9_ggSYEs8A8GB59-egdmJQJ+y0_yhsTcA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=aqm@ietf.org \
--cc=bloat@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