Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] cake exploration
Date: Mon, 13 Apr 2015 01:52:27 +0300	[thread overview]
Message-ID: <1463D1E1-794F-4998-9032-9CACE15D8E27@gmail.com> (raw)
In-Reply-To: <CAA93jw4z5kJdhUCVyTbee+k5_CYTxiY=Z_SjCD=pVPV38ScGng@mail.gmail.com>


> On 11 Apr, 2015, at 21:48, Dave Taht <dave.taht@gmail.com> wrote:
> 
> 15) Needs to work so an ISP can create service classes for their customers
> 
> DRR 1: cake bandwidth X
> DRR 2: cake bandwidth Y
> DRR 3:
> 
> I have no idea whether this can work at all, last I tried it DRR would
> stall everytime fq_codel had no packets to deliver.

Sounds like a classful version of cake.  I may have mentioned the need for something like it before, myself.

Actually, I think the required algorithms were already in cake1.  The key point is that you must track the backlog per class, and only accept the bandwidth grant from a class if there’s a backlog to service with it.  Even then, I had to backtrack if Codel goes and drops the last packet in the class, so that I could either select another class or reschedule the timer.

Cake3 simplifies that slightly, in that the “reschedule the timer” option is taken care of before class selection begins.

- Jonathan Morton

  parent reply	other threads:[~2015-04-12 22:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-11 18:44 Dave Taht
2015-04-11 18:45 ` Dave Taht
2015-04-11 18:47   ` Dave Taht
2015-04-11 18:48     ` Dave Taht
2015-04-11 19:12       ` Dave Taht
2015-04-12  2:33         ` Dave Taht
2015-04-12 22:52       ` Jonathan Morton [this message]
2015-04-12 23:14     ` Jonathan Morton
2015-04-13 15:54       ` Dave Taht
2015-04-12 22:44 ` 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=1463D1E1-794F-4998-9032-9CACE15D8E27@gmail.com \
    --to=chromatix99@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