Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	"cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Backporting 'tc class' support
Date: Mon, 16 Jul 2018 05:09:34 +0300	[thread overview]
Message-ID: <D2454C73-657B-45AA-BB4B-77A28807BD2D@gmail.com> (raw)
In-Reply-To: <DD9895DD-3236-41DB-B502-AD7916C070A9@darbyshire-bryant.me.uk>

> On 16 Jul, 2018, at 1:41 am, Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
> 
> AFAICT the tin order makes no difference whatsoever these days, indeed the dequeue mechanism picks up from the last tin and spins around rather than starting at either 0 or highest tin each time.

While it might not be entirely apparent from the code, the tin selector has two-phase behaviour, and this makes the tin ordering important.

If *any* tin contains traffic *and* meets its local schedule, the *highest* such tin is selected unconditionally.  Only if *no* such tin can be found does the search revert to finding the tin with traffic and with the most-nearly-satisfied schedule.  Both conditions are resolved on a single pass through the tin array.

In diffserv3/4, the Best Effort tin is set at the same rate as the global shaper.  Therefore, its local schedule is always met whenever the global schedule is.  Therefore, if it were placed higher in the tin list than Bulk, it would be able to strictly starve out Bulk traffic, which is not what I want.  Instead I give Bulk the next higher tin and a very restrictive schedule.

 - Jonathan Morton


  reply	other threads:[~2018-07-16  2:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-14 21:50 Toke Høiland-Jørgensen
2018-07-15  0:48 ` Kevin Darbyshire-Bryant
2018-07-15  9:48   ` Toke Høiland-Jørgensen
2018-07-15 20:13     ` Kevin Darbyshire-Bryant
2018-07-15 20:23       ` Toke Høiland-Jørgensen
2018-07-15 22:41         ` Kevin Darbyshire-Bryant
2018-07-16  2:09           ` Jonathan Morton [this message]
2018-07-16  4:00             ` Dave Taht
2018-07-16  9:24               ` Toke Høiland-Jørgensen
2018-07-16  9:30             ` Toke Høiland-Jørgensen
2018-07-16  9:57               ` Jonathan Morton
2018-07-16 10:18                 ` Toke Høiland-Jørgensen
2018-07-16 12:06                   ` Georgios Amanakis
2018-07-16 12:28                     ` Toke Høiland-Jørgensen
2018-07-16 12:44                       ` Kevin Darbyshire-Bryant

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=D2454C73-657B-45AA-BB4B-77A28807BD2D@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=kevin@darbyshire-bryant.me.uk \
    --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