From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] pie aqm finally landed in Linux
Date: Mon, 20 Jan 2014 10:46:24 -0500 [thread overview]
Message-ID: <CAA93jw4K7-cjxcXt+PWqXe5BMp+Fe8LL=RqyZqhLnL=ASViyLg@mail.gmail.com> (raw)
http://www.spinics.net/lists/netdev/msg264935.html
Hat off to vijay and the pie folk at cisco who shepherded the code
through 5 releases to get it upstream!
PIE is now mandated in DOCSIS3.1 cablemodems and the ECO for DOCSIS
3.0 went out a while ago.
I think the mandate differs from the Linux implementation. I don't
know the size of the recomended cablelabs target nor the size of the
estimation window (?)).
So that will improve going-upstream buffering problems dramatically.
The linux implementation supports ECN, the DOCSIS standard does not.
The ECN work in pie has some minor problems that fq_codel doesn't
have, we hope to discuss at ietf...
I will fold the v5 implementation of pie into cerowrt in the next release and
see what happens.
NOW:
The biggest problem remaining in cable is fixing excessive downstream
buffering. Surely something can be done to remove the 1.6 seconds of
buffering I observed yesterday (at some level without needing to AQM?
Some workaround that operators can use?). Some benchmarks I ran last
night (not against pie):
http://snapon.lab.bufferbloat.net/~d/bev/comcast_native_ipv6/
I sure hope the gpon, lte, and wifi folk are paying attention.
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next reply other threads:[~2014-01-20 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 15:46 Dave Taht [this message]
2014-01-20 18:56 ` Aaron Wood
2014-01-21 23:55 ` Greg White
2014-01-22 0:16 ` Juliusz Chroboczek
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='CAA93jw4K7-cjxcXt+PWqXe5BMp+Fe8LL=RqyZqhLnL=ASViyLg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--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