From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages-3.10] 5a8c9b: Teach SQM hotplug tricks
Date: Tue, 03 Mar 2015 04:32:49 -0800 [thread overview]
Message-ID: <54f5a9f17a2f6_62de3f8b56c792c0549f7@hookshot-fe2-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages-3.10
Commit: 5a8c9b17e46c696ad9015289f81a081a16e961a8
https://github.com/dtaht/ceropackages-3.10/commit/5a8c9b17e46c696ad9015289f81a081a16e961a8
Author: Sebastian Moeller <moeller0@gmx.de>
Date: 2015-03-03 (Tue, 03 Mar 2015)
Changed paths:
M net/sqm-scripts/Makefile
M net/sqm-scripts/files/usr/lib/sqm/run.sh
M net/sqm-scripts/files/usr/lib/sqm/simple.qos
Log Message:
-----------
Teach SQM hotplug tricks
Some interfaces like wan-pppoe go away, when the ppp connection is lost
and get recreated once the link is established again. SQM now
has its own hotplug script to re-enable itself on the interfae just hotplugged.
SQM will not touch other instances of itself running on other interfaces
if called by hotplug.d. The implementation now allows this functionality by
calling run.sh like:
/usr/lib/sqm/run.sh interface YOUR_INTERFACE_NAME_HERE
e.g.: /usr/lib/sqm/run.sh interface ge00-pppoe
If called with a specific interface SQM will only try to disable itself
on that interface to clean up all left over state and the re-enable
itself on just that interface. Hopefully that allows for better service
with instable interfaces like pppoe. The current code passes a simple manual
stop start test of the ge00-pppoe interface from the GUI and does seem
to do the right thing, at least on cerowrt 3.10.50-1...
reply other threads:[~2015-03-03 12:32 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=54f5a9f17a2f6_62de3f8b56c792c0549f7@hookshot-fe2-cp1-prd.iad.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