From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages] 45fe49: Updated debloat script to the one in the deBloat r...
Date: Sat, 28 Jan 2012 09:24:21 -0800 [thread overview]
Message-ID: <4f242f4526110_43c83fd01b684af43778@sh1.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages
Commit: 45fe492e371e248263e5ba8ee71a62ddc1e1d541
https://github.com/dtaht/ceropackages/commit/45fe492e371e248263e5ba8ee71a62ddc1e1d541
Author: Dave Taht <d@taht.net>
Date: 2012-01-28 (Sat, 28 Jan 2012)
Changed paths:
M net/debloat/Makefile
A net/debloat/files/debloat
M net/debloat/files/debloat.hotplug
Log Message:
-----------
Updated debloat script to the one in the deBloat repo
No longer do we modify txqueuelen, but enable sfq on all
interfaces with an equivalent packet limit (40), to what
we were using for txqueuelen.
While this is a decent idea for ethernet, it
will have side effects on packet aggregation.
The debloat script needs a conf file format designed.
My principal purpose in this is to thoroughly exercise the
new qdiscs, and also make sure that the interfaces STAY
modified with the new qdiscs when brought up and down.
reply other threads:[~2012-01-28 17:24 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=4f242f4526110_43c83fd01b684af43778@sh1.rs.github.com.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