Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] openwrt build with latest cake and other qdiscs
Date: Sun, 10 May 2015 18:29:56 +0100	[thread overview]
Message-ID: <554F9594.60808@gmail.com> (raw)
In-Reply-To: <554F64E1.6000609@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 903 bytes --]

Hi again

I tested Dave's build of cake on wndr3800.  (Didn't try specifying 
cake2/cake3; I'm guessing tc cake means cake3 on there).  "atm" 
adjustment worked fine on my adsl.  I can't distinguish it from 
sqm-scripts with the same configuration.

SQM seems to win from having "overhead 40", which I can't configure in cake.


	

up / kbit/s

	

down / kbit/s

	

overhead / bytes

	

Median RRUL / ms

SQM

	

16000

	

950

	

0

	

74

Cake

	

17175

	

995

	

0

	

76


	


	


	


	


Cake

	

16000

	

950

	

0

	

74

SQM

	

17175

	

995

	

40

	

70


	


	


	


	


DSL sync rate

	

17619

	

1020

	


	

59


IMO it wouldn't hurt for 'tc atm', 'tc adsl', and everything else to 
default to 'overhead 44'.  (The highest overhead Seb reported; the 
original worst case overhead[1] plus a vlan header for IPTV).

Alan

[1] http://ace-host.stuart.id.au/russell/files/tc/tc-atm/#usage

[-- Attachment #2: Type: text/html, Size: 14090 bytes --]

  reply	other threads:[~2015-05-10 17:30 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-10 14:02 Alan Jenkins
2015-05-10 17:29 ` Alan Jenkins [this message]
2015-05-10 20:37   ` Dave Taht
2015-05-10 20:38     ` Dave Taht
2015-05-11  6:54       ` Sebastian Moeller
2015-05-10 21:46   ` Sebastian Moeller
2015-05-10 22:19     ` Dave Taht
2015-05-11  6:50   ` Sebastian Moeller
2015-05-11  7:01     ` Jonathan Morton
2015-05-13  6:43       ` Jonathan Morton
2015-05-14  9:19         ` Sebastian Moeller
2015-05-14 10:24           ` Jonathan Morton
2015-05-14 10:33             ` Alan Jenkins
2015-05-14 10:42               ` Jonathan Morton
2015-05-14 10:58             ` Sebastian Moeller
2015-05-14 13:12               ` Jonathan Morton
2015-05-14 14:57                 ` Sebastian Moeller
2015-05-14 15:32                   ` Jonathan Morton
2015-05-14 18:15                     ` Sebastian Moeller
2015-05-14 22:06                       ` Jonathan Morton
2015-05-15  2:27                         ` Dave Taht
2015-05-15 21:49                           ` Jonathan Morton
2015-05-14  9:50   ` Alan Jenkins
2015-05-18  0:49     ` [Cake] More overhead keywords Jonathan Morton
2015-05-18  7:27       ` Sebastian Moeller
2015-05-18  8:13         ` Jonathan Morton
2015-05-18  8:41           ` Sebastian Moeller
2015-05-18 19:41           ` David Lang
2015-05-18 19:57             ` Dave Taht
2015-05-19 10:14               ` Kevin Darbyshire-Bryant
2015-05-23  0:30       ` Dave Taht
2015-05-23  2:27         ` Jonathan Morton
  -- strict thread matches above, loose matches on Subject: below --
2015-05-05  8:50 [Cake] openwrt build with latest cake and other qdiscs Dave Taht

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

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=554F9594.60808@gmail.com \
    --to=alan.christopher.jenkins@gmail.com \
    --cc=cake@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