Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Stranger target behaviour
Date: Sun, 1 Nov 2015 17:05:45 +0100	[thread overview]
Message-ID: <FCEE1CCE-7E06-4990-8638-E13F113515F2@gmx.de> (raw)
In-Reply-To: <563611DE.5080304@darbyshire-bryant.me.uk>

Dear friends of cake,

On Nov 1, 2015, at 14:21 , Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:

> On 01/11/15 09:47, Sebastian Moeller wrote:
>> Hi there,
>> 
>> On Oct 31, 2015, at 21:29 , Dave Taht <dave.taht@gmail.com> wrote:
>> 
>>> The second one is from the interval >> 4, which equates to 6.2ms. I
>>> note I picked that because some early data (2012) we had showed that
>>> target slightly greater than cable media acquision (6ms) time was a
>>> slight win, and it did not hurt to use a number more evenly divisible
>>> in binary than the arbitrary 5%.
>> 	Well, but should it not be 6.2ms even if no rtt is explicitly requested? Currently cake has a lot of corner-cases that are not too well documented either.
> Sebastian as ever picks up on the exact source of my confusion/point.
> 
> If 'target=interval/16' is the new mantra then the defaults built in to
> cake qdisc should be changed, otherwise we have the current situation
> which is:  Default Interval=100ms, target=5ms.  If I specify rtt 100ms
> via the joys of tc, then I have: Interval=100ms, target=6.2ms.  If I
> specify a target keyword such as 'internet' which also has an interval=
> 100ms, then target become 5ms again.  Somewhat inconsistent.

	I believe I just fixed this by initializing target in sch_cake to "interval >> 4”, I opted for the calculation instead of the simple number 6250 to sort of document the pattern and tried to put in a comment explaining why this is okay with codel's theory. Please note, I did not really test this, so for all I know it might break spectacularly...
	Slightly different question, I have a few cosmetic changes for tc, so which repository to commit this too, is tc-adv to be the gathering point for changes to be considered?

Best Regards
	Sebastian

  reply	other threads:[~2015-11-01 16:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-31 19:35 Kevin Darbyshire-Bryant
2015-10-31 20:29 ` Dave Taht
2015-11-01  9:47   ` Sebastian Moeller
2015-11-01 13:21     ` Kevin Darbyshire-Bryant
2015-11-01 16:05       ` Sebastian Moeller [this message]
2015-11-01 17:18         ` Kevin Darbyshire-Bryant
2015-11-01 17:48           ` Sebastian Moeller

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=FCEE1CCE-7E06-4990-8638-E13F113515F2@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cake@lists.bufferbloat.net \
    --cc=kevin@darbyshire-bryant.me.uk \
    /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