From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] AICP
Date: Sat, 4 Aug 2018 12:53:38 +0300 [thread overview]
Message-ID: <EDD734B6-27CD-422A-9D51-7D63169050A9@gmail.com> (raw)
In-Reply-To: <CAA93jw4yzBexnpAmN7HgujEcujReRsLKux5m_MX9CfHUXpWfdg@mail.gmail.com>
> On 4 Aug, 2018, at 11:11 am, Dave Taht <dave.taht@gmail.com> wrote:
>
> https://sci-hub.tw/10.1109/CNSM.2014.7014160
Looks like an advance over the status quo (as illustrated by Google's paper) with respect to policers. The basic TBF-type policer is pretty crap; really not hard to do better if you bother to think about it.
I'm still not *entirely* convinced that we can't have real DRR++/Codel implementations at line rate in hardware. I think nobody has even seriously tried to do it. Getting to that point would potentially obsolete policers overnight, at least from a theoretical point of view.
Meanwhile, we can still do a lot at the gigabit-per-subscriber level in software.
- Jonathan Morton
prev parent reply other threads:[~2018-08-04 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 8:11 Dave Taht
2018-08-04 9:53 ` Jonathan Morton [this message]
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=EDD734B6-27CD-422A-9D51-7D63169050A9@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@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