From: GitHub <noreply@github.com>
To: cerowrt-commits@bufferbloat.net
Subject: [dtaht/Cerowrt-3.3] 55092d: Enable low latency tcp by default
Date: Tue, 21 Feb 2012 05:07:32 -0800 [thread overview]
Message-ID: <4f439714b2765_2f7d3f834bfdeaf4345f0@sh1.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/Cerowrt-3.3
Commit: 55092d6c2bcaf6eff9941b78287f45bd7b33618d
https://github.com/dtaht/Cerowrt-3.3/commit/55092d6c2bcaf6eff9941b78287f45bd7b33618d
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-02-21 (Tue, 21 Feb 2012)
Changed paths:
A target/linux/ar71xx/patches-3.3/920-Enable-tcp_low_latency-by-default.patch
Log Message:
-----------
Enable low latency tcp by default
In the general case I have been going for low latency
over throughput. I have to note that to do more realistic
tests, turning off some of the low latency features such
as this one would be a good idea for some tests.
However, 'low latency by default' is to be preferred
for now.
Commit: f6ac928011f7aaf30b1a8ecc86a7ac571291258f
https://github.com/dtaht/Cerowrt-3.3/commit/f6ac928011f7aaf30b1a8ecc86a7ac571291258f
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-02-21 (Tue, 21 Feb 2012)
Changed paths:
A target/linux/ar71xx/patches-3.3/0002-Toss-wireless-traffic-marked-interactive-into-VI-que.patch
Log Message:
-----------
Toss traffic marked interactive into VI queue.
I have had multiple versions of this patch - one that did full blown
diffserv lookup, another that ripped out diffserv classification
entirely inside the wireless driver, to this one...
I'm not even sure if this version is correct.
Compare: https://github.com/dtaht/Cerowrt-3.3/compare/a42c870...f6ac928
reply other threads:[~2012-02-21 13:07 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=4f439714b2765_2f7d3f834bfdeaf4345f0@sh1.rs.github.com.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@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