Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Pete Heist <pete@heistp.net>
Cc: Dave Taht <dave.taht@gmail.com>,
	cerowrt-devel@lists.bufferbloat.net,
	 bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] beating the drum for BQL
Date: Thu, 23 Aug 2018 12:51:42 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1808231249160.23215@uplift.swm.pp.se> (raw)
In-Reply-To: <999D19F8-7E27-47CB-BC14-06193CC40943@heistp.net>

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

On Thu, 23 Aug 2018, Pete Heist wrote:

>
>> On Aug 23, 2018, at 2:49 AM, Dave Taht <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>
>
> https://community.ubnt.com/t5/EdgeMAX-Beta-Blog/New-EdgeRouter-firmware-2-0-0-alpha-2-has-been-released/ba-p/2414938 <https://community.ubnt.com/t5/EdgeMAX-Beta-Blog/New-EdgeRouter-firmware-2-0-0-alpha-2-has-been-released/ba-p/2414938>

My only experience with these devices is the Edgerouter 3/5/X, and they 
have very low performance if you disable offloads (which you need to do to 
enable AQM) and run everything in CPU, around 100 megabit/s of 
uni-directional traffic.

Do they have other platforms where this would actually matter?


-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

  reply	other threads:[~2018-08-23 10:51 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 [this message]
2018-08-23 11:38     ` Pete Heist
2018-08-24 17:13   ` Pete Heist
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=alpine.DEB.2.20.1808231249160.23215@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=pete@heistp.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