Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Cake List <cake@lists.bufferbloat.net>
Subject: [Cake] Why are target & interval increased on the reduced bandwidth tins?
Date: Wed, 24 Jun 2020 14:33:39 +0000	[thread overview]
Message-ID: <8ABBBE20-5045-41CF-967A-CD8961400ABE@darbyshire-bryant.me.uk> (raw)

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

Genuine question.  For the reduced bandwidth tins in diffserv3/4/8 a different rate and hence different target & interval values are also calculated.  I get why a target/interval calculation is desirable for the ‘main’ tin - this forms a ‘best case’ of how long each byte takes to transmit and is fundamental to the shaper.  What I’m less clear on is why increased targets & intervals are used for the reduced threshold tins.

To my mind it means those tins can be more ‘bursty’ before codel jumps on them.  That’s possibly ok on an egress path but I’m not so convinced on an ingress path.

Please point out the error in my thinking!


Cheers,

Kevin D-B

gpg: 012C ACB2 28C6 C53E 9775  9123 B3A2 389B 9DE2 334A


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2020-06-24 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-24 14:33 Kevin Darbyshire-Bryant [this message]
2020-06-24 14:40 ` Sebastian Moeller
2020-06-25 13:40   ` Kevin Darbyshire-Bryant
2020-06-25 20:42     ` Jonathan Morton

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=8ABBBE20-5045-41CF-967A-CD8961400ABE@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --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