From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/deBloat] 54cf80: Sub-4Mbit uplink operation is rather intractable
Date: Mon, 06 Feb 2012 19:03:50 -0800 [thread overview]
Message-ID: <4f3094961ebee_606a3fc124b892f82336eb@sh1.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/deBloat
Commit: 54cf8090be3bcb35aa4d493b3df450313c2c0519
https://github.com/dtaht/deBloat/commit/54cf8090be3bcb35aa4d493b3df450313c2c0519
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-02-06 (Mon, 06 Feb 2012)
Changed paths:
M src/debloat
Log Message:
-----------
Sub-4Mbit uplink operation is rather intractable
I sat down, fiddled and measured, and am back to accepting
long delays for big flows and FQ for short ones in the sub 10Mbit
realm.
I'm no longer as enthused about sfqred as I was. A real packet
orientation seems required for uplinks that consist mostly
of acks... maybe I can fiddle with avpacket?
I also managed to lock up an x86 box with choke + qfq + htb.
reply other threads:[~2012-02-07 3:03 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=4f3094961ebee_606a3fc124b892f82336eb@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