From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages] 82ef2f: Update babel 1.3.1, add patch for ECN
Date: Sat, 11 Feb 2012 05:55:43 -0800 [thread overview]
Message-ID: <4f36735f3365a_43bc3ffbba52b2f0579c2@sh1.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages
Commit: 82ef2faf9b711d6b929e7eaa545d8aa4fe61ebf8
https://github.com/dtaht/ceropackages/commit/82ef2faf9b711d6b929e7eaa545d8aa4fe61ebf8
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-02-11 (Sat, 11 Feb 2012)
Changed paths:
M net/babelz/Makefile
R net/babelz/patches/001-babeld-prio.patch
Log Message:
-----------
Update babel 1.3.1, add patch for ECN
This updates babel to git head, which is 1.3.1 based.
Julius disagrees with me as to the need to mark routing packets
with ECN, on a system that is doing probalistic dropping.
He may be right. In my own case, the 'vision' is to ultimately
find some sort of congestion indication on given routes via
the qdisc(s).
Commit: 92a1e08211256235692c8f5486023d466647b753
https://github.com/dtaht/ceropackages/commit/92a1e08211256235692c8f5486023d466647b753
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-02-11 (Sat, 11 Feb 2012)
Changed paths:
A net/babelz/patches/0001-Mark-packets-as-ECN-capable.patch
Log Message:
-----------
Missed the ECN patch entirely.
At some point I would like to be checking for ECN+ECT getting
turned on in multiple userspace based programs, mostly for
logging purposes. Also trying to detect what sorts of
streams get probalistically marked.
This isn't that, merely turning on the ECT bit.
Compare: https://github.com/dtaht/ceropackages/compare/36281bf...92a1e08
reply other threads:[~2012-02-11 13:55 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=4f36735f3365a_43bc3ffbba52b2f0579c2@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