From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages] ef0d86: Relentless TCP
Date: Wed, 04 Apr 2012 16:30:26 -0700 [thread overview]
Message-ID: <4f7cd992d4906_623a3fc1bb1eaafc29758@sh1.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages
Commit: ef0d868425e5e6c01a356b3ffceafa67115b8129
https://github.com/dtaht/ceropackages/commit/ef0d868425e5e6c01a356b3ffceafa67115b8129
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-04-04 (Wed, 04 Apr 2012)
Changed paths:
A net/kmod-tcp-relentless/Makefile
A net/kmod-tcp-relentless/patches/0001-updated-makefile-for-more-modern-boxes.patch
Log Message:
-----------
Relentless TCP
Matt Mathis, 2008
Relentless TCP is designed to maintain a standing queue at some network
bottleneck. It does so without regards to other traffic, and thus it is not
generally fair to other network users. It MUST NOT be used unless the network
is designed to actively control it to protect other flows and the Internet at
large from its aggressiveness.
To protect other flows, the network carring Relentless TCP traffic has to
implement Scavenger Service, Fair Queuing, Approximate Fair Dropping, or some
other capacity allocation algorithm.
To protect the Internet at large the network carring Relentless TCP traffic
has to be a physically or logically isolated from the rest of the Internet.
Be espically warry of the potential for dynamic routing to choose an
alternative path that can not adiquiately contol Relentless TCP.
To minimize the risks associated with Relentless TCP, it has to be enabled on a
per-connection basis.
reply other threads:[~2012-04-04 23:30 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=4f7cd992d4906_623a3fc1bb1eaafc29758@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