Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: "Frits Riep" <riep@riepnet.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Status of SQM-Scripts integration into OpenWRT Barrier Breaker?
Date: Mon, 25 Aug 2014 14:53:53 +0200	[thread overview]
Message-ID: <878umc7mse.fsf@toke.dk> (raw)
In-Reply-To: <000601cfc061$51474660$f3d5d320$@riepnet.com> (Frits Riep's message of "Mon, 25 Aug 2014 08:37:21 -0400")

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

"Frits Riep" <riep@riepnet.com> writes:

> I may be misunderstanding, but I thought this was a goal. Am I
> incorrect, or have the plans changed?

Don't think the plans have changed per se. More of a case of needing
more testing to be included in Openwrt.

There's some discussion of this here:

https://github.com/dtaht/ceropackages-3.10/issues/8

Testing is welcome!

> · I believe fq-codel is integrated into the latest available versions
> of Linux. If so, other than setting upload and download limits, do we
> already have buffer control handled with all newer OpenWRT releases?

Yes, fq_codel is included in the Linux kernel, and in Openwrt it is even
the default. So if your router is actually at the bottleneck
(physically), things should pretty much just work (in theory). However,
most routers are *not* at the bottleneck; there tends to be a modem of
some sort (whether cable, DSL or FIOS) in-between. Which is where
software rate-limiting (which is what SQM-scripts do) comes into play.

> · If so, do we still need to download and configure the packages,
> QOS-Scripts, and Luci-App-Qos? If so, do these packages do anything
> besides allow the configuration of Upload and Download limits?

Well, the QoS-script packages have some downsides and some upsides. The
main upside is configurability, I think. Including things like manually
classifying traffic etc. The downside is that it doesn't do IPv6 right,
and that SQM-scripts does link layer adaptation right, which I don't
think QoS-scripts do. Also, QoS-scripts is more complex and harder to
configure (I think).

> · If we can, in fact, control bufferbloat with OpenWRT and the latest
> Qos-scripts and Luci-App-QOS, then would the integration of SQM into
> OpenWRT provide much benefit in controlling bloat? If so, are there
> still plans to make that happen.

Well, I do believe there would be some merit to having SQM included (at
least as an optional package) in openwrt. More testing is the main thing
required, I think. And if we aim at completely replacing QoS-scripts,
(some of) the configurability needs to be added to SQM.

> I am very happy with the configuration of my home router running
> CeroWRT on a Netgear WNDR-3800 (running close to the latest build), on
> a Verizon FIOS connection at 75 Mbs Down / and 75 Mbs Up, and on
> running pings with Speedtest notice a definate difference in latency
> (very tight control) vs up to 100 ms latency.

Is this with SQM enabled? That usually tops out at around ~50Mbps due to
CPU limits...

-Toke

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

  reply	other threads:[~2014-08-25 12:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-25 12:37 Frits Riep
2014-08-25 12:53 ` Toke Høiland-Jørgensen [this message]
2014-08-25 13:12   ` Sebastian Moeller
2014-08-25 21:07   ` 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=878umc7mse.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=riep@riepnet.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