Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: bloat@lists.bufferbloat.net, Dave Taht <dave.taht@gmail.com>,
	cerowrt-devel@lists.bufferbloat.net,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] sqm deployment
Date: Fri, 15 Jun 2018 22:38:35 +0200	[thread overview]
Message-ID: <B9756672-AEBC-4F29-9CBA-4E4C3D506B84@gmx.de> (raw)
In-Reply-To: <CAA93jw6-OjOr2qvF=eca6O1uS-Zxg1+tK1S+yiSQ4hBMiUA+mQ@mail.gmail.com>

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

Question: does anybody know what hides behind eero's sqm name?

Best Regards
         Sebastian

On June 15, 2018 8:03:33 PM GMT+02:00, Dave Taht <dave.taht@gmail.com> wrote:
>I didn't know streamboost was still a thing.
>
>https://www.snbforums.com/threads/list-of-smart-queue-management-sqm-routers.47183/
>
>And I like very much that reviewers are at least asking the bufferbloat
>question
>
>https://www.macobserver.com/tips/how-to/best-mesh-wireless-system/2/
>
>but that's out of date.
>
>eero just added sqm. google wifi has fq_codel in it (but not sqm)
>
>What would it take to get more reviewers asking the bufferbloat fixes
>question?
>
>-- 
>
>Dave Täht
>CEO, TekLibre, LLC
>http://www.teklibre.com
>Tel: 1-669-226-2619
>_______________________________________________
>Bloat mailing list
>Bloat@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/bloat

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

  parent reply	other threads:[~2018-06-15 20:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 18:03 [Cerowrt-devel] " Dave Taht
2018-06-15 18:33 ` [Cerowrt-devel] [Bloat] " Jonathan Morton
2018-06-15 20:38 ` Sebastian Moeller [this message]
2018-06-22  5:32   ` Dave Taht
2018-06-22  6:02     ` Jonathan Morton

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=B9756672-AEBC-4F29-9CBA-4E4C3D506B84@gmx.de \
    --to=moeller0@gmx.de \
    --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