From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages-3.3] b3512e: Reorganize the Queueing Discipline configuration t...
Date: Wed, 18 Dec 2013 14:04:24 -0800 [thread overview]
Message-ID: <52b21be8de8ab_6d1ebadd581038d@hookshot-fe2-pe1-prd.aws.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages-3.3
Commit: b3512ecb5e0631b6d10b798fb226d42c6ce6665d
https://github.com/dtaht/ceropackages-3.3/commit/b3512ecb5e0631b6d10b798fb226d42c6ce6665d
Author: Sebastian Moeller <moeller0@gmx.de>
Date: 2013-12-18 (Wed, 18 Dec 2013)
Changed paths:
M luci/luci-app-aqm/files/aqm-cbi.lua
M net/aqm-scripts/files/usr/lib/aqm/functions.sh
M net/aqm-scripts/files/usr/lib/aqm/run.sh
M net/aqm-scripts/files/usr/lib/aqm/simple.qos
M net/aqm-scripts/files/usr/lib/aqm/simple.qos.help
M net/aqm-scripts/files/usr/lib/aqm/simplest.qos
Log Message:
-----------
Reorganize the Queueing Discipline configuration tab
The Queueing Discipline tab in the default state did only show a blank check box.
To let the user know what is configured expose the queueing discipline and
the queue setup script unconditionally. The ECN settings stay hidden under control
of the advanced configuration checkbox. The "Show Dangerous Configuration" check box
now allows to define one string for ingress and egress each that is appended
to each tcx command line setting up each qdisc (under AQM control).
This allows easier access to the more specalized options of each qdisc for testing and research.
Since there is no checking whatsoever perfomed on these two strings
ths option is truely for experts and hence dangerous.
reply other threads:[~2013-12-18 22:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52b21be8de8ab_6d1ebadd581038d@hookshot-fe2-pe1-prd.aws.github.net.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@lists.bufferbloat.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