General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Greg White <g.white@CableLabs.com>
To: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] pie aqm finally landed in Linux
Date: Tue, 21 Jan 2014 23:55:56 +0000	[thread overview]
Message-ID: <CF043B29.2656F%g.white@cablelabs.com> (raw)
In-Reply-To: <CAA93jw4K7-cjxcXt+PWqXe5BMp+Fe8LL=RqyZqhLnL=ASViyLg@mail.gmail.com>

Dave,

We're allowing target to be configurable, but providing a default value of
10ms.  In the DOCSIS CM implementation of PIE we don't track historic data
rates via an estimation window, instead we utilize the state of the token
bucket rate shaper to predict the rate transitions from the known peak
rate (power boost) to the known sustained rate.  This is both a) much
simpler and b) much more accurate.

The 3.1 spec and the 3.0 ECO do include AQM requirements for the CMTS side
as well. I agree though that reductions in buffer sizes would seem to be a
quick fix in advance of AQM implementations.

FYI, we've made some additional enhancements to the PIE algorithm for
DOCSIS since publication of the D3.1 spec.  An update is forthcoming.

-Greg


On 1/20/14, 8:46 AM, "Dave Taht" <dave.taht@gmail.com> wrote:

>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
>_______________________________________________
>Bloat mailing list
>Bloat@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/bloat


  parent reply	other threads:[~2014-01-21 23:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 15:46 Dave Taht
2014-01-20 18:56 ` Aaron Wood
2014-01-21 23:55 ` Greg White [this message]
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=CF043B29.2656F%g.white@cablelabs.com \
    --to=g.white@cablelabs.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@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