From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/deBloat] 243e3a: UPLINK support for htb_sfq_red
Date: Thu, 23 Feb 2012 08:48:28 -0800 [thread overview]
Message-ID: <4f466ddcafafa_7f143f91b36fcaf0166171@sh1.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/deBloat
Commit: 243e3a32edc59f556e5e06e678bbb55be4b08e29
https://github.com/dtaht/deBloat/commit/243e3a32edc59f556e5e06e678bbb55be4b08e29
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-02-23 (Thu, 23 Feb 2012)
Changed paths:
M src/debloat
Log Message:
-----------
UPLINK support for htb_sfq_red
While the baseline numbers are decent for 4-6Mbit uplinks, they
are probably too high for less than that.
reply other threads:[~2012-02-23 16:48 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=4f466ddcafafa_7f143f91b36fcaf0166171@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