[Codel] [Bloat] Latest codel, fq_codel, and pie sim study from cablelabs now available

[Dan Siemon]

On Thu, 2013-05-02 at 15:04 +0300, Jonathan Morton wrote:
> I can easily see a four-tier system working for most consumers, just
> so long as the traffic for each tier can be identified - each tier
> would have it's own fq_codel queue:
> 
> 1) Network control traffic, eg. DNS, ICMP, even SYNs and pure ACKs -
> max 1/16th bandwidth, top priority
> 
> 2) Latency-sensitive unresponsive flows, eg. VoIP and gaming - max 1/4
> bandwidth, high priority
> 
> 3) Ordinary bulk traffic, eg. web browsing, email, general purpose
> protocols - no bandwidth limit, normal priority
> 
> 4) Background traffic, eg. BitTorrent - no bandwidth limit, low
> priority, voluntarily marked, competes at 1:4 with normal.

The above is close to what I implemented:
http://git.coverfire.com/?p=linux-qos-scripts.git;a=blob;f=src-3tos.sh;h=3e88c2fa5f2feb0163c052086541ba17579a3c37;hb=HEAD

The above aims for per-host fairness and three tiers per host. Each tier
has an fq_codel QDisc (configurable).

Some performance results can be found at:
http://www.coverfire.com/archives/2013/01/01/improving-my-home-internet-performance/

It's pretty easy to configure the Transmission Bittorrent client to mark
packets.