Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Pete Heist <pete@heistp.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Bloat] beating the drum for BQL
Date: Fri, 24 Aug 2018 17:13:57 -0000	[thread overview]
Message-ID: <8E4244B7-C0AE-43D6-980F-C2370E662845@heistp.net> (raw)
In-Reply-To: <999D19F8-7E27-47CB-BC14-06193CC40943@heistp.net>

[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]


> On Aug 23, 2018, at 10:26 AM, Pete Heist <pete@heistp.net> wrote:
> 
>> On Aug 23, 2018, at 2:49 AM, Dave Taht <dave.taht@gmail.com <mailto:dave.taht@gmail.com>> wrote:
>> 
>> I had a chance to give a talk at broadcom recently, slides here:
>> 
>> http://flent-fremont.bufferbloat.net/~d/broadcom_aug9.pdf <http://flent-fremont.bufferbloat.net/~d/broadcom_aug9.pdf>
> 
> Thanks for sharing, this is really useful, raising awareness where it matters. Quite a bit of content... :)
> 
> Ubiquiti needs some work getting this into more of their products (EdgeMAX in particular). A good time to lobby for this might be, well a couple months ago, as they’re producing alpha builds for their upcoming 2.0 release with kernel 4.9 and new Cavium/Mediatek/Octeon SDKs. I just asked about the status in the EdgeRouter Beta forum, in case it finds the right eyes before the release:
> 
> https://community.ubnt.com/t5/EdgeRouter-Beta/BQL-support/m-p/2466657 <https://community.ubnt.com/t5/EdgeRouter-Beta/BQL-support/m-p/2466657>

This started a discussion, and no, so far it looks like there’s no BQL support in the upcoming 2.0 release.

For my own benefit, re-reading the original patch series comment (https://lwn.net/Articles/469652/ <https://lwn.net/Articles/469652/>) makes it sound like BQL is useful even without AQM (original benchmarks were done with straight pfifo_fast). I didn’t realize this, actually. If anything incorrect about BQL was said in this discussion, correct us, please… :)

Pete


[-- Attachment #2: Type: text/html, Size: 2585 bytes --]

  parent reply	other threads:[~2018-08-24 17:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23  0:49 [Cerowrt-devel] " Dave Taht
2018-08-23  5:47 ` [Cerowrt-devel] [Bloat] " Mikael Abrahamsson
2018-08-23 13:06   ` Sebastian Moeller
2018-08-23  8:26 ` Pete Heist
2018-08-23 10:51   ` Mikael Abrahamsson
2018-08-23 11:38     ` Pete Heist
2018-08-24 17:13   ` Pete Heist [this message]
2018-08-24 17:30     ` Dave Taht
2018-08-24 18:43       ` Dave Taht

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8E4244B7-C0AE-43D6-980F-C2370E662845@heistp.net \
    --to=pete@heistp.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@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