Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Running Cake at long RTTs
Date: Tue, 27 Oct 2015 21:04:03 +0200	[thread overview]
Message-ID: <8C854819-448B-42F9-850C-5B85D7885CFE@gmail.com> (raw)
In-Reply-To: <87a8r4mji9.fsf@toke.dk>


> On 27 Oct, 2015, at 17:14, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> 
> - Turn the hard packet queue size into a lower bound rather than an
>  upper bound.
> 
> - Scale the target to be 1/16th of the interval.
> 
> The first change allows Cake to actually reach the target throughput,
> but it still takes a long while to get there. With the second change, we
> actually get the desired behaviour.

The first change implies that the 10K packets * MTU default (ie. 15MB) isn’t big enough, but the 50MB calculated by 4 * RTT * rate is.  That’s a fairly narrow range, which suggests that the latter calculation is correct.

However, have you tried it with just the second change and not the first?  Conventional wisdom suggests that 15MB (which is slightly more than one BDP) should be about the right size for a buffer under these conditions.  I don’t want to gain a false impression of what the minimum usable buffer size is.

Limiting it to 10K * MTU was a safety valve to avoid the buffer size exploding.  With the first change in place, the “interplanetary” setting effectively removes any limit on buffer size as well.  This makes me deeply uncomfortable.  Instead, we should arrange to configure the safety-valve limit when accommodating LFNs.

The result from the second change is more clearly beneficial, but I’ll put it in userspace (ie. tc) rather than in the kernel.  I think the patch as given has some unintended consequences.  Scaling target with interval also means I have to take more care with the threshold calculation, since the threshold scales with the product of the two.

 - Jonathan Morton


  parent reply	other threads:[~2015-10-27 19:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 15:14 Toke Høiland-Jørgensen
2015-10-27 15:16 ` Loganaden Velvindron
     [not found] ` <6499FF74-D13B-4B2E-90E3-D1FDD3FD1468@gmx.de>
2015-10-27 16:50   ` Toke Høiland-Jørgensen
2015-10-27 17:14     ` Sebastian Moeller
2015-10-27 19:04 ` Jonathan Morton [this message]
2015-10-27 23:57   ` Toke Høiland-Jørgensen
2015-10-28  9:36     ` Sebastian Moeller
2015-10-28 15:28 ` Sebastian Moeller
2015-10-28 15:36   ` Toke Høiland-Jørgensen
2015-10-28 15:50     ` Sebastian Moeller
2015-10-28 16:34       ` Toke Høiland-Jørgensen
2015-10-28 17:44         ` Sebastian Moeller
2015-10-29 17:36 ` Kevin Darbyshire-Bryant
2015-10-30 20:30   ` Kevin Darbyshire-Bryant
2015-10-30 21:34   ` 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=8C854819-448B-42F9-850C-5B85D7885CFE@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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