From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages] ae1dd1: Added tcp-ledbat v9 kernel module
Date: Tue, 14 Feb 2012 20:06:25 -0800 [thread overview]
Message-ID: <4f3b2f41c194c_5feff35ae8760ef@sh2.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages
Commit: ae1dd1b5038e90b14405f682b9e3e4218a3eea0b
https://github.com/dtaht/ceropackages/commit/ae1dd1b5038e90b14405f682b9e3e4218a3eea0b
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-02-14 (Tue, 14 Feb 2012)
Changed paths:
A net/kmod-tcp-ledbat/Makefile
Log Message:
-----------
Added tcp-ledbat v9 kernel module
TCP-ledbat is an implementation of the v9 specification
for ledbat (otherwise known as the successor protocol to
bittorrent). It is hoped that this protocol will co-exist
better as a background protocol vs tcp.
While the simulations looked good, an implementation that
was independently testible on real world devices is better.
The tcp-ledbat implementation can be used by ANY tcp program
(wget,rsync, web servers, etc) - which should make it easier
to create and evaluate testible scenarios.
Commit: 900a65ad63b20cf1675053a7101d48945d3ddaef
https://github.com/dtaht/ceropackages/commit/900a65ad63b20cf1675053a7101d48945d3ddaef
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-02-14 (Tue, 14 Feb 2012)
Changed paths:
A net/dnsmasq/Makefile
A net/dnsmasq/files/dhcp.conf
A net/dnsmasq/files/dnsmasq.conf
A net/dnsmasq/files/dnsmasq.init
Log Message:
-----------
Merge branch 'master' of github.com:dtaht/ceropackages
Compare: https://github.com/dtaht/ceropackages/compare/3069ea8...900a65a
reply other threads:[~2012-02-15 4:06 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=4f3b2f41c194c_5feff35ae8760ef@sh2.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