Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@bufferbloat.net>
To: Hannu Nyman <hannu.nyman@iki.fi>
Cc: OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
	cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [OpenWrt-Devel] [RFC PATCH] packages: Smart Queue Management for AQM Packet Scheduling and Qos from CeroWrt
Date: Wed, 8 Oct 2014 20:01:25 -0700	[thread overview]
Message-ID: <20141009030125.GA19113@lists.bufferbloat.net> (raw)
In-Reply-To: <54359A46.8000107@iki.fi>

On Wed, Oct 08, 2014 at 11:10:46PM +0300, Hannu Nyman wrote:
> Dave Taht wrote on Thu Oct 2 03:49:15 CEST 2014:
> > So I don't know where to go. Certainly I'd like to see the battle
> hardened sqm scripts (which are more flexible than the C code above)
> get more widely used and in BB.
> 
> SQM seems to work ok with the current Chaos Calmer trunk.

Well, for now... I'd expect the delta to break eventually...

> 
> I have included your SQM in my trunk WNDR3700/3800 community build (
> https://forum.openwrt.org/viewtopic.php?id=28392 ) and it works ok.
> Arokh has also picked it up for his build (
> https://forum.openwrt.org/viewtopic.php?id=50914 ). So you might get
> more feedback sooner or later, if users of our builds really do try
> it.

Excellent. I'd *really* like to get some testers doing ingress shaping
at above 60-80mbits, which seems to be a brick wall we've hit on
the ar71xx and octeon, on other platforms like the arm and x86.

A tool we use a lot is netperf-wrapper.

> I feel that the best way to get wider testing and real-life usage
> for SQM would be to create a pull request in the new packages feed
> in Github, to get both the SQM itself and the Luci frontend included
> there. Being available in the packages feed would create more
> interest for the package. If it proves to work ok, the devs might
> then import it into the core Openwrt repo (where the old qos-scripts
> is).

I went to sleep pre BBrc1. I woke up, and everything was in github.

It's still not clear to me how I'd build cero from frozen BB sources,
rather than the evolving github packages.

> 
> 
> Ps. For my own build I made a slight modification to the Luci menu> item, as pure "SQM" does not say much. I changed it to "SQM QoS".
> 

Yes, SQM by itself doesn't mean enough.

  parent reply	other threads:[~2014-10-09  3:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1396119385-16871-1-git-send-email-dave.taht@bufferbloat.net>
     [not found] ` <1396119385-16871-2-git-send-email-dave.taht@bufferbloat.net>
     [not found]   ` <CAFE24U3s=z4jZkXMFU4xUyPyQ5fj95zOVxS7oBHGFuOp-FKXqw@mail.gmail.com>
     [not found]     ` <20140330222952.GA26806@lists.bufferbloat.net>
     [not found]       ` <542C2786.6090704@gmail.com>
2014-10-02  1:49         ` Dave Taht
2014-10-02  3:46           ` Alpha Sparc
2014-10-02 11:54             ` David Lang
2014-10-02 14:05             ` Sebastian Moeller
2014-10-06 16:02               ` Richard A. Smith
2014-10-06 19:41                 ` Sebastian Moeller
2014-10-09 16:42                   ` Richard Smith
2014-10-09 17:57                     ` Sebastian Moeller
2014-10-09 18:05                       ` Luis E. Garcia
2014-10-09 20:59                         ` Sebastian Moeller
2015-02-13  2:02                           ` Luis E. Garcia
2015-02-13  4:46                             ` Dave Taht
2015-02-13  5:13                               ` Luis E. Garcia
2014-10-09 18:13                       ` Dave Taht
2014-10-09 18:14                         ` Sebastian Moeller
     [not found]           ` <54359A46.8000107@iki.fi>
2014-10-09  3:01             ` Dave Taht [this message]
2014-10-09 17:09               ` Richard Smith
     [not found]             ` <CABXqzy77--kb59nedBnN+cLFGftN+gnBMJ9vi_xE8niP5YHEHw@mail.gmail.com>
2014-10-09  3:23               ` 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=20141009030125.GA19113@lists.bufferbloat.net \
    --to=dave.taht@bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=hannu.nyman@iki.fi \
    --cc=openwrt-devel@lists.openwrt.org \
    /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